If AI ships 8x more code, why do most side projects still die at 80%?
Anthropic published their own numbers recently. Not a vendor pitch — the company that builds the model, talking about its own engineers. Task-completion capability roughly doubling every four months. Over 80% of their own production code now written by their model. Engineers shipping 8x more per quarter than last year.
First reaction: if the people building the thing are moving 8x faster, what's even left for the rest of us?
Second reaction, after sitting with it: that's the wrong question, and the same piece answers why.
There's an independent study (METR) that measured regular developers using AI on real repos and found the opposite — 19% slower, not faster. Both are real. The difference is that Anthropic's number comes from a team with code review, merge gates, and engineers deciding what actually ships wrapped around the model. Without that, the model alone doesn't get you the 8x — METR's devs didn't have it, and it showed.
Which is exactly the shape of the gap I keep seeing in side projects. The build stopped being the hard part a while ago. What's missing when a project dies at 80% was never "the code doesn't work." It's nobody playing the role Anthropic's engineers are playing for their own codebase — deciding it's actually done, and closing the loop.
One line from the piece, from someone inside Anthropic on a day the automation worked almost too well: "nothing I do matters, everything is automated." Followed a few paragraphs later by the correction: "the comparative advantage of humans as of right now is still in seeing the bigger picture."
Not the code. The bigger picture — what ships, what doesn't, and whether it's real yet.
AI tracks. A human reads. If you've got something sitting at 80% right now, that's not a tooling problem you're missing — it's the same gap Anthropic's own numbers just made visible at scale.
