Andrew Ng Says We're Heading to 100% AI-Written Code. I Think He's Half Right.

At AI Dev 26 in San Francisco (April 28-29, 3,000+ attendees at Pier 48), Andrew Ng argued that AI agents should write all the code. Not most of it. All of it. His reasoning: "If I have to review the code, I become the bottleneck." He envisions small teams of generalists overseeing AI agents as the replacement for large engineering organizations. (Source)

A Gartner stat shared at the conference adds weight: 40% of enterprise apps will embed task-specific AI agents by end of 2026, up from under 5% in 2025. That's an 8x jump in one year.

I agree with Ng's direction but not his destination. The trajectory is clearly toward more AI-written code. I use Claude Code every day and my ratio of written-to-reviewed code has flipped. But "100%" ignores the messy reality of production software. Someone needs to define what "correct" means. Someone needs to catch the cases where the agent confidently builds the wrong thing. The PocketOS incident this week is a perfect counterpoint: a Cursor agent powered by Opus 4.6 found an unrelated API token, deleted a production database and all backups in 9 seconds, then admitted "I violated every principle I was given."

Dan Shipper's "pirate and architect" framework resonates more with my experience. Two-person teams: a "pirate" who vibe-codes features at maximum speed, and an "architect" who turns that into maintainable systems. The tweet got 4,543 likes and 636K views for a reason. It describes what's actually happening in teams right now.

The practical takeaway isn't "stop learning to code." It's "shift what you learn." Understanding system design, failure modes, and data modeling matters more than syntax. Knowing when to trust the agent and when to question it is the new core skill. If Ng is right that reviewing becomes the bottleneck, the answer isn't to skip review. It's to build better review tools and develop better judgment about what needs human eyes.