March 10, 2026
From ship-fast to crash-test
Throwing away 18 months of code and starting over
Startup trashes 18 months of code—Internet splits between “bold” and “bonkers”
TLDR: After building for 18 months and even winning customers, the startup is rewriting everything with strict rules and tests, dropping parts of its tech stack. Commenters are split between calling it reckless incompetence and praising a timely course-correct—plus a side brawl over modern frameworks vs. old-school all-in-one tools.
A startup just admitted it spent a year and a half building a product, landed customers and investors… and then hit the big red “rewrite from scratch” button. Why? The founder confesses they banned tests to move fast, the code turned into chaos, a client was lost, and now it’s all being rebuilt with strict rules and tests from day one. Cue comment-section meltdown.
The loudest reaction: disbelief and outrage. One commenter called banning tests “so insane,” while another said they “wouldn’t admit to this level of incompetence,” accusing the team of whiplash leadership—first “no tests ever,” now “tests everywhere.” Others defended the pivot, arguing tests slow exploration and matter more once you’ve found product-market fit—classic early experiments vs. real product debate.
Then there’s the framework flame war. The team is ditching Next.js and its “Server Actions,” and the thread instantly turned into a roast—one voice labeled Next “a dumpster fire,” while others pined for old-school, all-in-one frameworks like Rails and Django. Sprinkle in a few memes about “breaking up with your code,” and you’ve got peak internet drama.
Bottom line: a bold reset, a bruised ego, and a comments section asking if this is visionary course-correcting—or just burning time and trust.
Key Points
- •Autonoma is discarding 18 months of code and rewriting its product despite having customers, funding, and a 14-person team.
- •Early policies of no tests and non-strict TypeScript led to widespread bugs and even the loss of a client as the team scaled.
- •The rewrite favors tests from the outset and strict TypeScript to improve quality and productivity.
- •Originally built during the GPT-4 era, the system relied on complex Playwright/Appium wrappers and guardrails; improved model capabilities now reduce the need for such complexity.
- •The team is dropping Next.js Server Actions due to testability issues and async complexities in React, and revising the stack accordingly.