Simon Willison Admits He Stopped Reviewing Agent-Generated Code. 660 HN Comments Later, Nobody Has a Good Answer.

Simon Willison has been writing software for over 25 years. He's one of the most disciplined, transparent engineers in the Python ecosystem. And yesterday he published an essay admitting he no longer reviews every line of code that Claude Code generates for his production projects.

The essay hit 611 points and 660 comments on Hacker News, which tells you something about the nerve it struck. Willison frames it as "normalization of deviance," borrowing the term from aerospace safety research. Each time an unreviewed deployment works fine, the threshold for what requires review drifts upward. He went from 200 lines a day to 2,000, and somewhere in that 10x acceleration, the review habit broke.

What makes this different from the usual "AI coding is dangerous" take is that Willison isn't arguing against the practice. He's documenting the psychology of it. The productivity gain is real. The accountability gap is also real. He doesn't pretend to have reconciled them.

The HN thread split roughly into three camps. Camp one: "Just write better tests and let the agent run." Camp two: "You're building technical debt that will kill you in 18 months." Camp three, the quietest and most honest: "I'm doing the same thing and I don't know how I feel about it."

Meanwhile, over on Reddit, a post titled "the part nobody warns you about" hit 634 upvotes on r/ClaudeAI, describing the vibe coding debugging trap: 3 days to build, 2 weeks to debug. Supporting data from industry surveys says 63% of devs spend more time debugging AI-generated code than writing it manually.

And then there's the meta-analysis that landed on arXiv the same day: 23 studies aggregated, showing a ~24% throughput gain on average with AI coding tools. But the METR randomized trial buried inside it found experienced open-source developers were 19% slower with AI assistance. That's not a typo. The people who know the codebase best got slower when an AI was "helping."

I use Claude Code every day in my personal projects. I've felt exactly what Willison describes. The moment you stop reviewing isn't a decision. It's an erosion. And the kicker is that testing alone doesn't solve it, because AI-generated code can pass tests while being structurally wrong in ways that only matter six months later.

Andrej Karpathy's reframing matters here. His distinction between "vibe coding" and "agentic engineering" is precise: vibe coding is describing what you want and accepting what comes back. Agentic engineering is designing the system, specifying constraints, and using AI to accelerate implementation you've already reasoned through. The skills format he proposed is now spreading across GitHub as a way to encode that reasoning.

If you're shipping with AI tools, the question isn't whether to review. It's what your review strategy actually is, written down, before the next sprint starts.