lately. And I realized recently, I think we're all doing it wrong. Loops are really powerful, don't get me wrong. But so much of the discourse around them is hype driven and just really not helpful, right? We I think we have this idea just kind of as an industry somehow that we can like pipe a prompt in a loop to a coding agent and that we can build software this way, right? Maybe we're investing a lot of time in verifiers. Maybe you have six different code review agents. But at the end of the day, if we're doing this, we're still building 40,000 line PRs that just nobody wants to read, right? And this isn't to throw shade at Jeff Huntley, right? This is Ralph is an innovative uh it's a sharp tool that works very well for certain types of problems. It works very well if you're not building on a team. And it works very well if you're not working on critical systems. But most of us are working on teams and we don't fit in that box. So today I want to talk about how to build loops that work in large complex code bases. For systems that have real customers, real users, real regulatory obligations and service level agreements and everything else that keeps us from shipping YOLO 40,000 line PRs straight to production. In other words, I want to talk about how to build loops for the real world.