1 Comment
â­  Return to thread

I think that's a pretty interesting approach. My decision is pretty specific to my audience. A significant part of my audience is people who are just getting into programming, or people who have been at it for a while but are looking to level up. A lot of the value is in my archive, but a lot of the people who need what's in that archive are at a point in their career where they can't afford a number of newsletter subscriptions. So, I really want that archive available to those people when they need it.

I have a 3-5 year vision for my newsletter. As these subscribers do level up, I'm hoping to see them end up as paid subscribers 6 months, 1 year, 3 years from now. I've been a programming author for 10 years now, and I've had similar growth in more formal publication work.

If I were writing for an audience who already had expertise that should correlate to well-paying jobs, I might consider the opposite approach. I think it's *really* important for people to have a clear intended audience, and then find ways to sort out who your actual audience is. Then formulate a strategy that works for your audience, not just decide on random "growth hacks" or something.

Expand full comment