The Two-Year Publishing Cadence
Write a post several times a week for two years and an audience will find you
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 90%
A deceptively simple recipe for building an audience from nothing: pick a focused topic, publish regularly, and sustain it for two years. The magic isn't any single post — it's the accumulated body of work that eventually gets discovered, plus the compounding improvement in your writing.
Origin
Attributed by Orosz to Jeff Atwood (co-founder of Stack Overflow, author of the Coding Horror blog), whose post 'How to be famous on the internet' laid out the three-step recipe; Orosz applied it to build The Pragmatic Engineer.
Core principles
- 01Consistency over brilliance — the body of work compounds, not any single hit
- 02Focus the topic; a blog 'all over the place' attracts no one
- 03You write first for yourself, which guarantees you improve even if no one reads
- 04Discovery is lumpy and delayed — posts can surface months later
How to run it
- 1
Write a focused post
Publish a piece on a clearly defined topic (Orosz narrowed his scattered personal blog into one about software engineering under a dedicated brand, The Pragmatic Engineer).
Pro tip Buy a topic-specific domain/brand to signal focus and commitment.
Watch out A blog that's 'all over the place' gives no one a reason to follow it.
- 2
Repeat on a frequent cadence
Publish roughly a few times a week (Atwood's rule) — or a sustainable adaptation like every two weeks — and keep it up.
- 3
Sustain for about two years
Keep going for ~two years even when it feels like nothing is happening; the payoff comes from accumulated work being discovered, not immediate traction.
Pro tip Do it for yourself so you keep going through the quiet stretches — Orosz kept writing 'once every few months depending on my mood' but never fully stopped.
Watch out Expect to feel like giving up; Orosz did give up for months, then a post from six months earlier suddenly blew up on Hacker News.
In the wild
Orosz read Jeff Atwood's 'How to be famous on the internet' — write a blog post, do it three times a week, do it for two years, and you'll be famous. He rebranded his scattered blog as The Pragmatic Engineer, published six focused posts, then gave up. Months later a post ('a comment is an invitation for refactoring') exploded on Hacker News.
→ Software engineers argued over his work; he realized people cared, kept writing for years, and by newsletter launch had a large existing readership that converted fast — 100 subscribers day one, 1,000 paid within six weeks.
Common mistakes
Expecting fast results and quitting early
Orosz gave up after six posts, assuming no one cared — yet a post surfaced on Hacker News six months later. Judging the strategy on the first weeks misses that discovery and compounding take up to two years.
Publishing an unfocused grab-bag
His original personal blog was 'all over the place' and 'wasn't going anywhere' — without a defined topic, there's nothing for an audience to attach to.
Is it for you?
Best for
People with genuine expertise who want to build an audience but have no following yet
Not ideal for
Anyone needing income or validation within months, or unwilling to write consistently for years
From the transcript
“how to be famous on the internet I said like there's three simple steps there's one write a blog post two do this like three…”
“I'm kind of tired of my old block being all over the place and there's no focus and no one really cares about it”
“if you start writing and you do it regularly you know two things will happen”
“I had a huge traffic Spike and it crashed my my shared hosting at the time and it came from the site called Hacker News”
From the episode
Leaving big tech to build the #1 technology newsletter
Gergely Orosz (The Pragmatic Engineer)