The problem is not vibe coding. The problem is the people doing this were never good software engineers before vibe coding.
Simply put you still need good practices to produce working good code with AI.
Oddly what I have found best is patterns that many would cringe and demeans unit test and integration test.
Yes I still vibe unit test and integration test, but more than ever I have to put on my PM and QA hat, even more so with web dev.
For me the only part of the process that has changed is I don’t write the code. I still setup environments to run the code, I still manually poke at things I suspect will be fragile. But most importantly I still always run the software before shipping it.
Couldn't have said it better myself. Issue at hand is if you're working in an environment that enables such people and even encourages that behaviour. Suddenly, their voice is the same where it was never even a whisper before, and you can't do anything about it. It is extremely demotivating and I would actually propose a more radical approach to it - either embrace the shit in full and commit to it as well or really do engage into another company where there's a better filter for hiring. The latter are usually smaller companies because they can't afford no to.