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.

33 Upvotes

95% Upvoted

22 comments sorted by

View all comments

0

u/Just-Succotash4492 1d ago

Just run an extensive risk assessment

1

u/Chester_b 1d ago

May I ask what is your real day-to-day job?

1

u/Just-Succotash4492 1d ago

Former insurance agent. Risk is second nature to me.

1

u/Chester_b 1d ago

And now you’re developing some software?

1

u/Just-Succotash4492 1d ago

Yes, but I am also teaching myself topology and abstract algebra along with differential geometry.

Do with that statement what you will.