Technical
Year Two of Daily Writing: Why I Stopped Chasing New Topics
Most content creators burn out in year two because they mistake novelty for value. I started year two of daily technical writing with a deliberate shift: fewer new topics, deeper versions of existing ones. The business result surprised me.
The Breadth Trap
Year one I wrote about everything. Django, Next.js, Claude Code, Cursor, DynamoDB, SES, WordPress, consulting sales, pricing, retainers. Each article stood alone. Readers got a buffet with no main course.
Year two I picked eight topics I care about and committed to going deeper on each one every month. The article count per topic tripled. The referral traffic from each topic tripled too.
What Depth Looks Like in Practice
- Instead of one article on Claude Code setup, twelve on specific workflows
- Instead of one article on DynamoDB basics, ten on cost, indexes, migrations
- Instead of one article on consulting sales, fifteen on specific objections
Depth stacks. A prospect reading one of my Claude Code articles finds eleven more. The compounding credibility that took eight months to build on breadth, builds in one month on depth.
The Topic Commitment Test
Before committing to a topic for year two, I applied a three-question test:
- Have I written about this at least five times already?
- Do clients ask me about this every month?
- Would I be bored writing twenty more articles on it?
If the answers were yes, yes, no, it made the list. Boring topics stay shallow. Interesting topics reward depth. The pattern held across every topic I evaluated.
The Search Consequence
Depth changes how search engines read your site. Twenty articles on one topic signals authority in a way one hundred articles across twenty topics never will. I watched my Claude Code page start ranking for long-tail queries within three weeks of going deep, even though the site had been publishing daily for eight months with broader coverage.
Google's own guidance aligns with this shift: see the search quality rater guidelines on topical authority for the reasoning.
The Internal Link Bonus
The other hidden benefit of depth is internal linking. Twenty articles on one topic give me twenty natural anchor points for every new article in that category. Year one my internal linking was scattered because my topics were scattered. Year two my internal linking is dense because my topics are concentrated. Search engines read that density as confidence.
What I Tell Other Writers
Write broadly for six to twelve months to find what you care about. Then pick a small number of topics and commit to depth. Breadth is the exploration phase. Depth is the exploitation phase. Most writers never exit exploration and wonder why their audience never forms. The transition is uncomfortable because it feels like narrowing, and narrowing feels like losing readers. It is actually the opposite: the readers you keep are the ones worth writing for.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read