Vom Prompting zum Loop-Design: Der Paradigmenwechsel bei KI-Coding

Here's your monthly reminder that you shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents. I don't know about y'all, but this memo didn't make it to me. Of course, I've seen loops before. Things like the Ralph loop really helped me think about how agents can do more over time. But it also massively increased the error rate of the changes that I was having my agents make. They were really cool, but they didn't seem that productive. And I found myself going back to the usual. And Pete, as always, is a bit ahead of the curve. I started getting my agents to prompt themselves. I started setting up systems where agents would review code, give feedback, adjust it, and then trigger re-reviews. I started using Hermes agent to bring context to me instead of to go out and find it for me. And I've accepted now that Pete's right. I would argue now that the majority of your agent runs should probably not be running with prompts that you wrote. That is a crazy thing for me to say because it was one of those like I never thought I would see the day things. But now that I've explored it myself and I've shipped a lot of code using these types of loops, I have a lot of thoughts. I want to share.