WTF Is a Loop? Part 2: The 15 Loops People Are Actually Using
Matt Van Horn · article
The concrete catalog that proves loop engineering is real adoption, not just a meme. 15 patterns grounded in actual usage — the fastest way to see what a loop looks like in the wild.
Don't Build More AI Agents Until You Watch This
Nate B Jones · youtube · ~14 min
The strongest counterweight to agent-sprawl thinking: before you build another agent, ask if a better loop would do it. Orchestration over proliferation.
Hamel Husain · youtube · ~5 min
Evals are the verification half of a loop — without them, a loop can only converge on what its feedback can see, which is nothing.
Inspect: Ramp Background Coding Agent (75% of Code)
@rahulgs · tweet
The bottleneck was not the model — it was the environment. Most of the work is making the codebase legible and the feedback fast and truthful. Inspect has the context and tools to prove its own work before results reach a human.
autoresearch: Remove Yourself as the Bottleneck
@karpathy · tweet
Remove yourself as the bottleneck, put in few tokens, huge amount happens. The cleanest one-line statement of what loop engineering is for — Karpathy's autoresearch loop as the existence proof.
Addy Osmani · article · ~9 min
The shift: you held the tool the whole time for two years. Now you build a small system that pokes the agents instead of you. The maker/checker split is the highest-value structural move — the model that wrote the code is too generous grading its own homework.
You Shouldn't Be Prompting Coding Agents Anymore — Design Loops
@steipete · tweet
The tweet that named the era: prompting is the old model. The new model is designing a system that does the prompting for you. 6.5M views in one week — the signal that a new discipline had found its name.
Loops are Replacing Prompts. Verification is About to Be Your Biggest Problem.
Arjun Iyer · article · ~7 min
A loop is not a cron job with better marketing. A cron runs a fixed script; a loop has a decision-maker in the body — a model that reads work state and chooses the next action. The engineering is everything you wrap around that decision so it converges on correct instead of wandering.
article · ~8 min
A useful loop specifies five things: trigger, action, proof, memory, and a stopping condition. Every entry pairs the prompt with a verify-and-stop note — the evidence that proves the work is done.