Verification is the job now

Not long ago I ran a hardening pass on a site and the build went green, every check passing, and if I'd trusted that green I'd have shipped a change that blanked the entire site to every visitor. The build had no way to see it. The failure only existed in the real rendering path, not the compile. The green checkmark told me the code ran. It said nothing about whether the code was right, and those turned out to be very different claims.

That gap is the whole reason this track exists, and it's the single biggest shift in how building works now. Generation got cheap. A model produces plausible, working-looking code faster than you can read it. Which means the bottleneck moved. It used to sit on "can you write this." Now it sits on "can you prove it's right," and that second half does not get faster just because the model got faster. If anything it got slower relative to generation, because there's now vastly more output flowing past you per hour, all of it looking finished.

Why is the review harder than the writing now?

Because writing produces one thing and verifying has to rule out everything else. When you wrote the code yourself, slowly, you verified as you went; the understanding and the artifact grew together. When a model hands you two hundred lines in three seconds, you have the artifact with none of the understanding, and you have to build the understanding backwards, against code designed to look correct. The model optimizes for output that reads as right, which is precisely the property that makes verification hard, because right-looking and right are the two things you now have to tell apart.

The reframe

You are not a person who writes code with AI help. You are a person who directs generation and then verifies it, and the verification is the part that's actually yours. The writing is increasingly the model's. The judgment about whether what it wrote is correct, safe, and actually solves the problem is the irreducible human job, and treating it as an afterthought, a quick skim before shipping, is how green builds blank production sites.

The takeaway: generation is cheap and verification is the bottleneck, so the review is the work now, not a formality after it. Budget for it like it's the job, because it is.