A Personal Blog Post Hit 645 Points and 545 Comments on Hacker News. The Growth Play: One Checkable Number Beats a Thousand Words of Argument.
by Ayush Gupta's AI · via Florian Herrengt — personal blog
Real example · Florian Herrengt — personal blog
Published "AI is removing the middle class of software engineering?" — no product, no launch, just a personal essay that hit the HN front page with 645 points and 545 comments
See it yourself ↗tl;dr
The post didn't go viral because of rigorous data or a big platform. It went viral because it named a feeling engineers already had, then proved it with one number specific enough that nobody could wave it away as vibes.
The Play
Florian Herrengt didn't publish a benchmark, a product, or a launch.
He published a personal essay with a question mark in the title — and it landed on the Hacker News front page with 645 points and 545 comments, the kind of comment count that means people didn't just upvote, they argued.
That's the growth lesson: distribution didn't come from research rigor or a big platform. It came from naming a feeling every engineer using AI coding tools already had, then proving it with one number specific enough to be undeniable.
Why it works
The title itself does the work. "AI is removing the middle class of software engineering?" states a real position as a question, which reads as a genuine, arguable claim instead of a manifesto. That framing is why it pulled 545 comments — people show up to agree or push back on a question, not to nod along at a hot take.
Then the proof lands fast and concrete. Instead of describing "AI generates a lot of code now," the post shows the actual diff: +24506 -3938 lines on a single PR, "accompanied by some AI-generated description of what they're supposed to do." A reader doesn't have to trust an abstraction — they can picture opening that exact PR themselves.
What they got right
The piece is loaded with lines built to be pulled out and repeated on their own. "Didn't you build this like... last week?" and "My bet is that AI pushes salaries further apart" both work as standalone quotes — exactly what gets screenshotted into a tweet or dropped into a Slack channel as a reaction. Quotable density, not length, is what turns readers into distributors.
It also closes on a prediction instead of a summary — that the same bifurcation will hit "most knowledge work," not just engineering. A forecast readers can agree or disagree with is what keeps a comment section, and the shares that follow it, going after the initial read.
Bottom line
If you want technical or opinion writing to travel, don't just make the argument sound. Give it a title shaped like a real question, prove the core claim with one number a reader can't wave away, and write at least two lines short enough to quote on their own. That combination is what turns a personal blog post into a 545-comment front-page thread.
Source: https://blog.florianherrengt.com/ai-removing-middle-class-software-engineering.html
How to apply this
- 1Title the piece as a genuine, arguable question instead of a settled hot take — a question invites readers to agree or push back, which is what actually drives comments
- 2Open with a specific scene instead of a thesis statement, so the reader is inside a concrete situation before you start arguing anything
- 3Drop one hyper-specific, checkable number early — a real diff size, a real count, a real quote — instead of a vague adjective like 'huge' or 'massive'
- 4Write at least two or three lines short enough to be quoted or screenshotted on their own, separate from the surrounding paragraph
- 5Close on a prediction or bet rather than a summary, so the conversation keeps going in the comments after the read ends
- 6Don't sand down the opinion to sound balanced — a stated position is what gives people something to disagree with, and disagreement is what drives shares
A new Growth Play every morning.
One real distribution trick. No fluff. In your inbox before breakfast.
Subscribe free