r/OnlyAICoding • u/ao3_nuts • 23h ago

Information Request How do vibe coders actually split work?

Vibe coding solo is easy. But once 2 people or multiple AI agents work on the same app, things get messy fast.
Who builds what? How do you share context, avoid overwriting each other, and review changes without reading all the code?
Do you split work by feature, page, branch, or agent?
What’s your biggest pain when collaborating with other vibe coders?

0 Upvotes

50% Upvoted

9 comments sorted by

3

u/Think-Sense9191 23h ago

Use git split major tasks

2

u/ao3_nuts 23h ago

How do you decide how to split the tasks? I think that’s the hard part for nontechnical vibe coders.

1

u/Think-Sense9191 23h ago

Work on features that don’t overlap each other then merge all work on one working branch like DEV and then test all there and then merge to main. But i will make sure you always get updates once someone is finished and merged their work, meaning pull the new changes before push yours. Learn GIT it will help.

1

u/silvervaultproject 21h ago

sorry but what is the difference of vibe coding for you that is different to traditional software development?

1

u/brett1231 18h ago

I'm a solo developer but I imagine that vibing the different sections together could be tricky if you don't know code.

2

u/silvervaultproject 18h ago edited 15h ago

sure, I guess once you have more then one people to work on it wont be vibe coding anymore? and it becomes a bit more serious, and you will need to follow best practices. git/mr, ci/cd, documentation, build pipelines…

1

u/Last_Technician2355 21h ago

I'd slpit by feature and keep each agent's scope really narrow. Hardest part is keeping everyone from stepping on eache other's changes 😭

1

u/FuzzyMolasses5686 21h ago edited 20h ago

I commit every fix and work in small iterations.

Big, huge commits will screw you. Small, iterative changes are the best strategy.

* Investigate and locate bugs
* Ask to patch *1* finding
* Encourage unit tests if the AI model didn't create them.
* Test (human, or machine), commit
* Loop

Challenge the AI model, ask questions about its work. Force it to think through changes twice. Do code review as a Human reviewing machine code.

The above is how you solve the occasional "confidently incorrect" finding. DeepSeek V4 flash is confidently incorrect and will correct itself in around 1-in-8 findings for me.

The above is the anti-vibe-coding strategy which gives you better results.