> Vibe coding there is a near guarantee the person doesn't know what the code does either.
Accepting code into the project when only one person (the author) knows what it does is a very bad idea. That's why reviews exist. Accepting code that zero persons know what it does is sheer screaming insanity.
Unless it's not important. I think vibe coding is fine for self-hosted weekend projects / hackathons / POCs and only if there's no intersection with legal stuff (like PII or payment processing).
But for any open source or enterprise project? Hell no.
If you don't ever need to know or maintain the code, sure, it's not your code, you don't own it, in fact the code is disposable. For something like POC, where I don't care how it's done, I just want to see if it can be done - I've done it myself. Then if real code is needed, you throw the disposable one out or rewrite it completely. That's fine. But if it's a long term project, somebody needs to own it.
Accepting code into the project when only one person (the author) knows what it does is a very bad idea. That's why reviews exist. Accepting code that zero persons know what it does is sheer screaming insanity.