The thing about that is, it doesn’t work.
Even enterprise Claude, even if you’re doing something routine, is still going to need shitloads of “fixing”.
The problem is that the vibe coders who doesn’t know wtf they’re doing isn’t going to know that there’s problems. They’re going to give the prompt, get something back. Try it. “Huh it doesn’t work!” And try it again.
Maybe they’re smart enough to figure out what the error is, get something new back, try it… find out it doesn’t work….
You see how that goes? Someone who’s experienced knows what they can pull from libraries and what they need to tweak to get it running, and don’t need it.
Guess whose code is going to be more stable and more effective with fewer vulnerabilities?
It’s a liability time bomb, and the reason tech savvy people are more hostile to it is because they’re the ones who know its capabilities.
Another negative is liability.
Let’s say your org providing, idunno, coding to control illumination for a smart facility.
Let’s say the lighting doesn’t work, and as a result some one slips and dies. Let’s say it’s 50/50 of the code is at fault or not.
Your org is now looking at liability in a wrongful death lawsuit.
Even if you can argue that it was being used wrong, it’s still going to cost your org more than it would have to pay some one who’s a proper coder to do it.