I completely agree with this take, and I'm saying that as someone who works at an AI company...

Vibe coding will rarely end well.

Using AI intelligently to speed up your development cycle, while understanding (and correcting) the plethora of places it goes wrong, requires a deep understanding of software engineering and architecture. Pure vibe coders rarely get this bit, and that's why it often ends badly.

I mean no offense, because I think AI can be a great and powerful tool. But it does not mean you don't need to study how good software is engineered, strictly define scope, and manage your AI like you would any other developer on the team, to ensure code quality and sane architecture.