Karpathy formalized "Software 3.0," and it's the most useful frame I've read this year

Andrej Karpathy published his Sequoia Ascent talk summary on June 17, and it gave me language for something I've been doing without a name. His framing: Software 1.0 automates what humans can specify as explicit rules. Software 2.0 automates what we can describe with training data. Software 3.0 automates what humans can verify. Anything checkable by a test suite, a game score, or a proof checker is now in reach of an agent.

The boundary is verifiability. Not capability, not model size, verifiability. If you can write a check that says "this output is correct," you can hand the task to an agent and let it grind. If you can't write that check, you're still doing the work yourself, or you're shipping unverified output and hoping. He pins December 2025 as the inflection point when agentic coding crossed from experimental to reliable, which roughly matches when my own usage flipped from "fun demo" to "I depend on this daily in my personal projects."

This is the conceptual spine the rest of today sits on. GLM-5.2 gives you a cheap, open verifier-and-generator. OpenCode gives you the harness to run the loop. Unreal gives agents a new surface where the verification is "does the scene render correctly." Karpathy tells you the meta-principle: invest in the checks, because the checks are now the boundary of what you can safely delegate.

It reframes where engineering effort goes. For fifteen years the scarce skill was writing the implementation. Now the implementation is cheap and the scarce skill is specifying what "correct" means precisely enough that a machine can verify it. That's test design, eval design, spec writing. It's also, and this is the part that matches my own experience, taste. Because a lot of what we verify isn't expressible as a unit test. "Is this UI good" doesn't have a proof checker. Human judgment is the verifier there, and that's exactly the part that doesn't automate away.

What to do this week: take one task you've been hand-coding and ask whether you can write a verifier for it. A test, an assertion, a schema check, a golden output. If you can, hand it to an agent and supervise the verifier instead of the code. If you can't, that's the signal that this task still needs you, and that's useful to know explicitly rather than by accident.