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•2h ago
I read their pitch as trying out multiple agents to do the same task and then pick your favorite approach
himeexcelanta•1h ago
I 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.
barbazoo•1h ago
You 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•6m ago
separate projects, working on multiple projects at once, I find context switching is a lot easier than having multiple agents on 1 project
sebdufbeau•1h ago
Couldn't find the info quickly, is the stealth model cheetah they had a few weeks ago their new Composer 1 model? If not, who's was it?
billconan•2h ago
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•2h ago
himeexcelanta•1h ago
barbazoo•1h ago
alexandargyurov•6m ago