The Three Mistakes of the AI Debate

Last month I spent 30 days letting AI write 100% of my code - a real SaaS, in production, no line of app code typed by me. Then I did the thing you're supposed to do after an experiment: I went and read what everyone else thinks is happening.

Mistake 1: Arguing about "Can AI Write Code?" When That Was Never the Bottleneck

Every post, on both sides, is secretly an argument about code generation. The optimists show a model one-shotting a working app. The pessimists show a model hallucinating an API that doesn't exist. Both think they're arguing about the future of the profession. They're arguing about typing.

Here's what 30 days of AI writing everything taught me: the typing was never the hard part. It just felt like it was. The AI wrote my CRUD, my Zod schemas, my scaffolding - flawlessly, faster than I ever could. And it changed my output by maybe 20%, because writing the code was 20% of the job.

Mistake 2: Treating the Skill Ladder as a Fixed Object

The optimist's argument: "Juniors + AI will be as productive as seniors, so we'll need fewer seniors and everyone levels up." The pessimist's argument: "AI does junior work, so junior jobs vanish and it's a bloodbath." Both of them are standing on the same hidden assumption - that the ladder from junior to senior stays where it is while AI rearranges who stands on which rung.

But the ladder is made of the work. You become a senior by doing ten thousand hours of exactly the work AI is now absorbing: the scaffolding, the boilerplate, the confident-but-wrong first draft you learn to distrust by being burned. That's not busywork you graduate past. That's the curriculum.

Mistake 3: Benchmarking on the Demo Instead of on 2am

Every prediction - hype and doom alike - extrapolates from a demo. The optimist's demo: watch it build a todo app in 90 seconds. The pessimist's demo: watch it fail a riddle. Both are the happy path. Both are the moment of the screenshot.

Production is not the screenshot. Production is 2am, a real user doing something weird, a database blip, a double-clicked button, an empty state nobody designed.

The Synthesis: Stop Predicting, Start Structuring

"Will AI replace developers?" is an unanswerable, and frankly boring, question. It's astrology for engineers. The useful question is structural, and it's answerable today: What has to be true for AI's output to be trustworthy?

My 30 days gave me the answer, and it has nothing to do with which model wins. The thing that writes the code can never be the thing that reviews it - a model grades its own homework and always passes. You need a separate reviewer whose entire job is to refute the diff, not bless it. You need a human on the merge button who can see the blast radius the model can't.

That's not a prediction. It's a structure. And it's the same structure whether the model is GPT-9 or something we haven't built yet, because it doesn't depend on the model being good - it depends on the model being checked.

The Real Question

So, honest question for the comments: which of the three mistakes have you caught yourself making? I made all three before the experiment beat them out of me - the demo one twice.