7 ms·
I don't understand multi-agent vibe coding. because with vibe coding, one can easily generate thousand lines of code in a short period of time. If we do this i
by billconan 11mo ago
I don't understand multi-agent vibe coding.
because with vibe coding, one can easily generate thousand lines of code in a short period of time. If we do this in parallel, merging the changes, resolving merge conflicts will be a nightmare. Unless, the agents work on completely isolated modules, but that's rarely the case?
- smb06 11mo agoI read their pitch as trying out multiple agents to do the same task and then pick your favorite approach
- himeexcelanta 11mo agoI might get this with ui/styling experimentation. But shouldn’t devs have an idea of what they’re building - the specific building blocks, logical, and data flows - before you prompt? I couldn’t imagine getting three different one shot attempts at an implementation and having to validate and read through each one.
- viraptor 11mo agoNot everything will work the first time. You could try 3 approaches and immediately discard the ones that don't pass tests. (Which is likely to be 1-2 of them)
- barbazoo 11mo agoYou could have them work in separate areas if it's in the same code base or just spread work across code bases. Not sure if that's a very efficient or enjoyable way to work but I'm assuming that's how you could scale it.
- alexandargyurov 11mo agoseparate projects, working on multiple projects at once, I find context switching is a lot easier than having multiple agents on 1 project
- samtrack2019 11mo agoI use git worktree for that... it's great