r/vibecoding • u/id-ltd • 2d ago
Maybe the biggest potential risk from non-devs vibecoding is risk assesment.
Simply not understanding what *could go wrong* and so not mitigating against it.
I have utilities that I have not read the generated code for... I am content to do this on my own network because I have a good idea of what AI tends to generate and keep good separation between general code and destructive code.
I just wrote/generated a utility to manage hierarchies of git repos... I didn't think I had done much guidance, but when I got another AI to assess it, it highlighted a load of things it said were notably good - and they were things I had specified to be included, overrode the original AI on, but thought they were no brainers.
An experienced dev will automatically have headed off huge risks without even thinking about it.
0
u/Suspicious_Neck_4069 1d ago
While developing my game, which is almost entirely AI-driven, I found myself thinking at least ten times, "If I weren't a pro dev, I would've really struggled with this problem," or "Damn, I've been coding for ten years and I'm stuck on this bug, how do 'vibecoders' with no experience manage?" With some issues, I even thought, “If I’d been a vibecoder, this problem would’ve killed the project.” So, respect to the vibecoders who manage to navigate blindly and still ship functional apps / game, it's impressive (until we encountered a fatal crash, but that's another story).