Ask HN: Any team-wide experience with vibe coding?
There is a lot of content out for vibe coding, but it mostly comes from solo devs. Are there teams who are vibe coding and how do they solve the general problem of trust.
Sure, vibing for myself is fine as I will suffer the negative consequences - but would you send PRs for code review if you haven't really worked on the code?
I like vibe coding for small solo stuff, but I am looking for experiences from people where multiple devs vibe code on the same codebase. My gut feeling is that it cannot really work when multiple people are involved. And, to be completely honest, I would neither feel good sending this code to someone nor I would like to review something vibe coded by someone else.
2 comments
As a team we all are vibe coding everything but since it is not a generally accepted practice at my workplace, we do make sure that the code that we push has been thoroughly checked before it is pushed. Also we are writing a lot more tests now and using AI code reviewers to make sure the MRs don't break anything critical.
My experience is that yes, vibe-coding allows to find out quickly what works - but then a real person is put onto implementing it properly and only then it becomes a PR for other people to see.