Karpathy at Sequoia: The Spec Is the New Code, and AI Output Is 'Awkward and Gross'

Andrej Karpathy stood up at Sequoia Capital's AI Ascent 2026 and said what a lot of us have been thinking but hadn't articulated this cleanly. He called the current era "Software 3.0," defined as prompting an LLM interpreter, and declared December 2025 the tipping point when agentic coding went from "helpful but messy" to consistently correct.

Then he called AI-generated code "awkward" and "gross."

He's right. I see it every day in my own workflow. Claude Code produces working solutions that make me wince. The code runs. It passes tests. It also reads like it was written by someone who learned programming from reading every Stack Overflow answer simultaneously. Variable names that are technically descriptive but miss the intent. Abstractions that solve a problem nobody had. Correct but graceless.

Karpathy's framing is that agents are interns who need supervision on "aesthetics, judgment, taste." The specification and the plan are becoming the actual code. You write a detailed document describing what you want, and agents execute it. The document IS the program.

This maps directly to my experience shipping three products last year. The bottleneck was never writing code. It was knowing what code to write and whether the output met my standard. My design background, 20+ years of visual communications before I went full-stack, turned out to be the competitive advantage I didn't expect. I can look at a component, a function, an architecture diagram, and feel whether it's right before I can explain why.

That intuition is what Karpathy means by taste. And it's the thing agents can't do yet.

His practical advice: invest in writing better specifications. Treat your project docs, your CLAUDE.md files, your architecture decision records as first-class code. Because increasingly, they are. The agent reads the spec. The agent writes the implementation. The human evaluates craft.

If you're a builder who's been spending your learning budget on new frameworks and languages, consider redirecting some of that toward technical writing and system design documentation. The spec is the new code. The person who writes the clearest spec gets the best agent output.