"vibe coding" by definition means you are not looking or understanding the generated code and you are accepting all changes and "fixes" by the AI.

In software engineering, you must understand what the code is doing and you will struggle to resolve sudden issues if you do not understand these systems which risk outages, loss of money, and data.

You do not want to be "vibe coding" software that is to be operating on planes. That would be disastrous.

> The days of Devs gatekeeping and shitting on good ideas because the syntax of a PR was not perfect are over.

Developers who do that without using a formatter are the bad ones anyway and are there to argue and waste your time.