Software engineering shifts to "loop" design as AI coding agents reshape development

Key takeaway

• Software engineering is undergoing a structural shift as AI coding agents become more capable.

• Rather than writing code themselves, engineers are increasingly designing "loops"—outer frameworks where humans set tasks and review results, with inner loops where AI agents execute the work.

• This transformation parallels broader changes in how people collaborate with AI, though its practical limits and security implications are still being tested by early adopters.

3 Key Points

FAQ

What is the difference between the inner loop and outer loop that Ronacher describes?

The inner loop is where an AI agent executes work—using tools, reading files, testing code, and learning from results before stopping. The outer loop (harness) is the human-controlled framework where engineers define the task, set safeguards, and monitor whether the AI has achieved the goal.

How are engineers currently implementing this loop-based approach in practice?

Early adopters are organizing tasks in Markdown files (PLAN.md, TODO.md) that AI agents can read and execute, and using project management tools like Linear to track tasks designed for loop-based workflows. Some teams are also experimenting with checklist-style tracking to communicate loop boundaries to AI systems.