← All IntelClip / AI AgentsSpeeding up a loop without losing reliability
From Loop Engineering from First Principles — Kyle Mistele, HumanLayer · ≈16:21
Concrete scaling options for a 150-procedure migration that would take six months one-at-a-time — batch selection with per-item context windows, or fan the workflow out to one PR per teammate.
What’s in it
- Concrete scaling options for a 150-procedure migration that would take six months one-at-a-time — batch selection with per-item context windows, or fan the workflow out to one PR per teammate.
Clip transcript
duplication, hopefully no conflicts. And of course, once you're feeling confident in the loop, we're going to want to speed it up, right? I have 150 RPC procedures to migrate. If I do one at a time, it's going to take 6 months, which is way longer than I want to wait. Fortunately, there's a lot of ways to pick up the the velocity of our loop. Uh we could have our controller pick three procedures to migrate instead of one at a time or five. Uh we could have our controller pick three or five and then do each of those in a separate implementation phase, which will be both cheaper and more reliable since each migration gets its own context window. Or we could just run the workflow four times and give one PR to each of four people on the team. So let's put it all together.
Comments
Sign in to comment.
Loading comments…