What is "Loop Engineering". Next : no prompting

In this edition:

1. What is a loop engineering, in plain English? The four parts every loop is built from, explained with a thermostat.

2. It began, naturally, with Ralph Wiggum. The Simpsons-inspired hack that started it all.

3. Then the hack became a feature. How vendors absorbed the pattern into their products.

4. What people actually run. Triggers, schedules, and the loops working right now.

5. The backlash arrived right on schedule. Drift, quality concerns, and rising bills.

6. Was the loop just scaffolding? The case that this was always temporary.

7. The boring skill that actually wins. What matters more than loops for most teams.

Boris Cherny has arguably logged more hours with AI coding agents than anyone alive. He created Claude Code, the tool that turned “let the AI write it” from a party trick into a workflow. So when he stood up at Anthropic’s developer conference this year and admitted he’d stopped prompting his own product, people paid attention.

He doesn’t type instructions anymore, he explained. Loops do it for him. “My job is to write loops.”