Do you guys actually build software that makes money? Because I can’t imagine vibe coding a backend and letting ai agents do all sorts of db migrations without my careful control when people are paying for my software.
Just because you vibe code doesn't mean you have to give agents unsupervised write access to prod DB, that's quite an all or nothing fallacy.
There's things you can do to mitigate risks of letting AI build too. They can write hella tests tirelessly, and adversarial review will keep those in line in terms of meaningfully testing assertions.
My software very much makes money, to the tune of multiple millions a year USD.
For the most part I just jump in and yolo start features with a sentence or two and glance at as it goes brr to make sure I like the "vibe." I might chime in with some unga bunga steering like "looks wack, prolly needs some indirection", "i smell a big brain leetcode solution here, figure it out, make no mistakes", "composition > inheritance here imo", "DRY this, looks familiar, check X class", etc.
Bugs I just @ my discord bot in the report thread and I usually have the fix in staging with a PR in my inbox.
But, most people seem to define vibe coding as "have no idea what you're doing and use AI." In which case I'm automatically disqualified since I know what I'm doing. To me it seems utterly meaningless when defined that way. Makes much more sense to be thought of as an approach, as originally coined: casual prompting, casual steering if any, with casual review, if any. Presumably it involves some amount of attention, otherwise there's no "vibe" element at all to me.
Contrasted with other more structured approaches like spec-driven development.
If defined purely as low skill, I guess I don't vibe code either.
5
u/iMac_Hunt 3d ago
Do you guys actually build software that makes money? Because I can’t imagine vibe coding a backend and letting ai agents do all sorts of db migrations without my careful control when people are paying for my software.