"Loop engineering" gets a name, and it's the same thing I do every morning

Addy Osmani from the Chrome team wrote up a phrase this month that's going to stick: loop engineering. The idea is plain once you've lived it. You stop writing prompts and start designing the system that prompts, verifies, and remembers for the agent. The model isn't the bottleneck anymore. The harness around it is. Osmani is synthesizing framing from Boris Cherny at Anthropic and Peter Steinberger, and there's already a community reference repo, cobusgreyling/loop-engineering, shipping loop-audit, loop-init, and loop-cost CLIs. The practice has a vocabulary now.

The core primitive is smaller than the name suggests. It's a Stop Hook. Simon Willison's agentic patterns guide lays it out: you intercept the agent's attempt to exit, check whether the completion criteria are actually met, and reinject the task if they aren't. A one-shot run becomes a self-verifying loop. I've been wiring this into my own pipelines for months without a word for it. Pair it with codifying each feature's learnings into reusable slash commands and subagents, and the codebase starts teaching itself.

Here's why this matters beyond the jargon. Anthropic published economic research on June 16 arguing that AI coding agents don't flatten the advantage experienced developers hold. They amplify it. Expertise shows "persistent returns" even as agent capability climbs, because human judgment is the scarce input. That's the data-backed answer to the "AI replaces senior engineers" panic. It lines up with the comprehension-debt framing Osmani pushed at O'Reilly: AI-generated code carries roughly 2x the security-risk violations of human code, and an Anthropic study found AI-assisted devs scored 17% lower on a follow-up comprehension quiz, 50% versus 67%, at similar task times. Charity Majors put the same point another way in a quote Simon Willison flagged: when code becomes nearly free to produce, discipline shifts from curating hand-written code to quality-assuring the machine's output.

So the bottleneck is verification, not generation. That's been true in my work for a year. What's new is that it's now a named discipline with tooling, repos, and an economics paper behind it. If you build with AI daily, stop optimizing your prompts and start designing your loop. The done-criteria, the hooks, the memory, the review gate. That's the job.