AI Builds the Code. You Still Have to Drive.

Why autonomous AI development still breaks down without human engineering judgment, architectural ownership, and quality oversight -a practitioner's honest take.

Every week there's another headline about AI writing better code, reasoning more deeply, or per Anthropic's own research, beginning to improve itself. The capability gains are real. The productivity lift is genuinely breathtaking. I've experienced it firsthand building publishi.ai and roiscale.ai, handling observability tooling, agentic pipelines, and content generation, mostly without writing a single line of code myself.

But there's a claim embedded in all of this I want to push back on: that you can hand the wheel to an AI agent and walk away with a usable product on the other side. You can't. Not yet. And probably not for longer than most people want to admit.

The thing nobody talks about enough is the usability gap. An AI can produce code that compiles, passes tests, and technically fulfills the spec. What it struggles to produce is software that feels right, interfaces that are intuitive, flows that make sense to a first-time user, interactions that don't require three seconds of puzzling before the action becomes obvious. For end-user products, that gap is often the entire gap between success and abandonment. AI does not experience the software it builds. You do. Your users do.

It's an F1 Car, Not a Self-Driving Car

The best analogy I have: working with AI coding tools is like graduating from a Toyota Corolla to a Formula 1 car. The speed is incomparable. But an F1 car does not drive itself. It demands a skilled, fully engaged driver who reads the track and makes decisions at high speed. Put it on autopilot and you end in a ditch. Guaranteed.

Staying in the driver's seat means a few things in practice:

Own the architecture: actually understand the data flow and component boundaries, not just approve the diagram, because the model will quietly diverge from it three sessions later and it will.

Know every technology the model recommends before it enters your stack; a suggestion is not a decision.

Be the institutional memory for your own system's principles, because the model has none - it will take the expedient path if you let it.

Validate every UI yourself, by actually clicking through it, because models think in logic and structure while humans experience software spatially and emotionally, and no amount of prompting closes that gap.

And stay open to AI-generated ideas, but treat them like suggestions from a junior engineer: good instinct, needs review.

AI tools have made me dramatically faster, and I have no intention of going back. But speed without control is just a faster crash.

The human in the loop isn't an optional enhancement. It's the load-bearing structure the whole thing rests on.

Don't leave the cockpit.