|
|
|
|
|
by JohnMakin
48 days ago
|
|
> So you should never just have one coding agent managing a piece of infrastructure. Not even for a low-stakes part of your business. You should always have at least two or three working together on a little crew. I know why people think this, and I went down this route early on, but I’m not sure this logic follows. Teams of agents, even adversarial ones reviewing work, are prone to the same types of mistakes as the problem they’re attempting to fix. In fact, mistakes at the adversarial/approval layer are so much worse, because the next stage assumes it was correct, and the error cascades. Maybe enough agents and tokens and context bring the probability of “correctness” closer to 1, but what is the judge of what is correct? what if that criteria is hallucinated? I’m not sure this concept has been proven. I’ve certainly been unable to prove it to myself, and I’ve tried very hard. |
|