Its just like playing chess against 6 players at the same time. Your job is to rotate fast enough to give them what to play while you keep verifying their assumptions and architectural decisions.
You are hitting a good point with context, but I worked in large teams before, so context was never actually there. With AI, that "context" becomes just the highest level of architrecture you can think of.. the rest is details that only the AI knows.
I have given up on the idea that I can find bugs in the AI code. If I set it up correctly, there won't be any actual bugs, just working behaviors that I don't actually want or missing features that I forgot to mention. Most of my day these days is just that.
Replies (5)
The thing with llms is they don't remeber anything either. So unless you write very good context/skills they will get lost and duplicate code. At least on big teams someone usually owns most parts of the code (even if contributors leave). I will be interested to see how it works out long term.
Yeah, you MUST write skills/experts on how to use the code. Otherwise it is never going to work well.
The AI can write those too. You can ask it to review the code, find patterns and write the texts. Reading all the code consumes a lot of tokens but if the skills are good that only need to happen once.
> there won't be any actual bugs
😂😂😂
I can't effectively play chess against 6 people. and if I did, they would mostly be waiting for me. Or I would lose. This is an insane metaphor
It's just practice, really. Once you get a hang of it, it becomes easy. It's much easier than managing the work of a small team of 6 people. Or taking care of 6 dogs at the same time, for instance.
