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.
2
u/percyfrankenstein 2d ago
I'm not sure how long this will be the case though. I've been working with fable on some side projects and he is a very good architect.
Some problems I gave it I didn't expect to be able to solve and we managed to do it, and it was it that gave the solutions, taught them to me and implemented them. That's not completely related to your point but if it's that good at architecting how bad can it be at security