

Yeah, there’s also the “debugging is just as hard as writing elegant code” side of things. Vibe coding is largely just putting yourself in a permanent debugging role.
The big issue I see with vibe coding is that you need to know best practices to build secure code. Even if you don’t adhere to them all the time, best practices exist for a reason. And a programmer who doesn’t even know them is a dangerous thing, because they won’t even be able to see what is insecure (until it’s far too late).
Studies have found that vibe coders tend to produce less secure code, but have higher confidence in their code being secure; It’s essentially Dunning-Kruger in practice. I’d have no issue with someone using AI to get the broad strokes down. But then they need to be able to back it up with actual debugging. Not just “I didn’t even bother looking at it. If it compiles, push it to prod.”
I’ve long said that every retail worker should be legally allowed to physically fight ten customers per year. And not a calendar year, where all the employees would be out of fights by the time holiday shopping season rolled around (or would be forced to save all of their fights for the holiday season). Give them ten points, and each point takes a year to fall off of their record once it is used. And the retail employee would have zero obligation to tell the customer if they have any points. Leave the customer guessing until the employee swings on them.
As gun nuts are so fond of saying: An armed society is a polite society. I think it would solve a lot of the problems with Karens. Karens only go full Karen because they hold all of the power in the relationship. But the threat of potential violence would go a long way towards quelling the most unreasonable ones, and people would only bother going full Karen if they truly felt they were justified and were willing to back it up with a fight.