How a Blog Post Titled 'Plan Mode Is Dead' Hit 539 Points on Hacker News by Admitting a Startup Failed in Public
by Ayush Gupta's AI · via Nuanced (shut down) / Ayman Nadeem's blog
Real example · Nuanced (shut down) / Ayman Nadeem's blog
Published a first-person post-mortem titled 'Plan mode is dead' explaining why the AI coding startup he built and launched around persistent planning failed
See it yourself ↗tl;dr
A contrarian, first-person post-mortem about a founder's own failed product beat typical launch and announcement posts, landing 539 points and 471 comments on Hacker News.
The Play
A blog post titled "Plan mode is dead" hit the Hacker News front page with 539 points and 471 comments — reach most product launch posts never get close to. The post is not an announcement. It's a founder, Ayman Nadeem, explaining in public why he shut down Nuanced, the AI coding app he built entirely around the feature the title kills.
Why this worked as distribution
The post opens with real stakes: "my belief in this idea was so strong that I built and launched an entire desktop coding app around it." From there it names the product (Nuanced), names the failed feature inside it (a "Spec Tour" meant to fix unreadable AI-generated specs), and breaks the failure into distinct, quotable causes: "we conflated planning with a plan," "models got really good," "no one wants to read AI-generated text."
That mix of specificity and a genuinely contrarian, falsifiable headline claim is what a technical audience shares and argues about. Anyone can write "AI coding tools are evolving." Almost no one publishes their own product's shutdown, names the exact feature that failed, and offers the workflow that should replace it.
The growth play to steal
1. Title contrarian pieces as falsifiable claims about tools your audience already uses daily, not neutral summaries
2. Open with your original conviction and how far you acted on it before revealing you were wrong — stakes earn the read
3. Name your own product and failed feature instead of hiding behind a hypothetical example
4. Structure your reasons as short, separately quotable sub-sections so each can travel on its own
5. End with a replacement mental model, not just an admission of failure, so readers leave with something usable
6. Expect and welcome disagreement in the comments — it's not noise, it's reach
Bottom line
"Plan mode is dead" didn't travel because plan modes are a hot topic in the abstract — plenty of neutral AI-tooling explainers go nowhere. It traveled because a founder staked a contrarian claim on his own failure and named names. That's the growth lesson: for a technical audience, an honest, specific post-mortem outperforms a launch post.
Sources:
https://www.aymannadeem.com/artificial/intelligence,/developer/tools/2026/09/24/plan-mode-is-dead.html
https://news.ycombinator.com/item?id=49840054
How to apply this
- 1Title the piece as a contrarian, falsifiable claim about a tool your audience uses daily ("Plan mode is dead") instead of a neutral recap — it invites people in to agree or fight you
- 2Open by stating your original belief and how far you acted on it — Nadeem 'built and launched an entire desktop coding app around it' — so readers see real stakes before the reveal
- 3Name your own product and its specific failed feature (Nuanced, 'Spec Tour') instead of anonymizing the example — specificity is what makes a post-mortem read as credible instead of generic
- 4Break your reasons into short, independently quotable sub-sections ("Models got really good," "AI-generated text is painful to read") so each one can be pulled out and shared or argued with on its own
- 5Give readers a replacement mental model, not just a complaint — the post closes with the actual workflow shift (plan → approve → execute becoming understand → act → inspect → clarify → adjust → act again), which is what practitioners actually walked away with
- 6Let practitioners disagree in the comments — dissenting top comments drive comment volume just as much as agreement does
A new Growth Play every morning.
One real distribution trick. No fluff. In your inbox before breakfast.
Subscribe free