The 10x productivity story is cracking, and the people saying so are the ones who ship

An essay titled "I Think I Have LLM Burnout" hit 359 points and 307 comments on Hacker News on July 8, one of the highest-engagement AI threads of the week. Developer Alec Scollon's argument is simple and it landed because a lot of people are quietly feeling it: constant AI-assisted coding left him mentally exhausted, because the work didn't disappear, it moved. The cost of writing code collapsed and the cost of reviewing, verifying, and steering the output went up.

This isn't one grumpy blog post. It's a pattern forming across people whose opinions I actually weight. Gergely Orosz used his Pragmatic Engineer AMA on July 8 to push a deliberately uncomfortable take: AI often doesn't make work easier, and people who find it effortless may not be pushing hard enough. He revealed he uses zero AI in his writing, Grammarly off, specifically to avoid skill atrophy, while consciously accepting that his hand-coding ability will degrade because he does use AI there. His own survey found about 30% of engineers report hitting AI usage limits. Kenton Varda from Cloudflare declared a moratorium on AI-written PR and commit descriptions after finding them "worse than useless," plausible filler that reviewers still have to wade through to find the real signal.

The data underneath is the part I keep chewing on. One DevOps analysis found 42% of teams report increased code-review conflict. The recurring thesis: leadership hears "10x" and triples sprint commitments while real output rises about 10%. That gap doesn't read as an individual failing. It reads as a systemic mispricing of what the tools actually deliver.

I'm not fully sure where I land on this. I use Claude Code every day in my personal projects and I'd never go back. But I've also had weeks where I shipped more and felt worse, where the fun part of the work, the actual thinking, got replaced by a review queue that never empties. The decision-fatigue framing names something real. Every accepted-or-rejected diff is a micro-decision, and hundreds of those a day is a different kind of tired than writing code was.

The move here is deliberate, not reflexive. Orosz's discipline of keeping one skill fully hand-worked to prevent atrophy is a real strategy, not luddism. Pick the skill you refuse to let degrade. And if you manage people, the sprint math is the thing to fix first. Triple the commitments and you're not getting 10x, you're getting burnout with a productivity dashboard on top.