Updated May 2026. A coworker pulled the workweek breakdown last Wednesday and showed it to me on Slack. 11.4 hours per week reviewing AI-generated code. 9.8 hours per week writing code by hand. The two numbers crossed sometime in late 2025 and nobody put up a sign. The first instinct is to call this an AI win — look how much we shipped! The second instinct, which takes longer to arrive, is the one that matters: review time is the bottleneck now, and review is the layer where you discover what's actually broken. This piece is about that second instinct. Specifically, about what review is asking developers to do that nobody trained them for, and the reason every "AI-native" testing tool you can name still doesn't fix it. What the verification gap actually is The verification gap is the distance between code that compiles, passes type checks, passes the test suite an AI agent wrote alongside it, and code that survives contact with a real user doing something the agent did not anticipate.…