Back to Podcast Digest
Matthew Berman12m

Only the best are using them...

TL;DR

  • Loops replace prompt-by-prompt coding: Instead of telling Claude or Cursor what to do each step, you define a trigger plus a goal, and the agent keeps iterating until it decides the goal has been met.

  • A loop needs only two parts: Berman reduces the idea to a trigger and a verifiable end state, such as passing tests, green CI, or an LLM-based judgment for fuzzier product goals.

  • The practical example is PR review and auto-fixing: In Cursor Automations, he sets a loop to run whenever a PR opens in AstroHub, review the code, fix issues, make tests pass, and commit changes back to the same PR.

  • The hard part is not coding, it is specifying the goal: Deterministic targets like "all tests pass" are clean, but "build this feature" often requires a full spec up front, which clashes with how many builders actually explore and refine features as they go.

  • Loop engineering is powerful but brutally expensive: Berman says only the "top 1% of 1%" are really using it today, pointing to Peter Steinberger's reported $1.3 million monthly token usage and the effectively unlimited budgets at OpenAI and Anthropic.

  • Automation is not the same as a loop: An automation just runs a sequence, while a true loop contains a decision about whether the goal has been reached, which is why Berman connects the idea directly to reinforcement learning.

The Breakdown

The new AI coding meta is not better prompts, it is loops: give an agent a trigger and a verifiable goal, then let it keep coding until the job is done. Matthew Berman argues this is where software engineering is headed, even if today only a tiny elite with massive token budgets can actually afford to use it seriously.

Was This Useful?

Share