Everyone talking about having them break it down into smaller chunk. Vibe coding there is a near guarantee the person doesn't know what the code does either.
That alone should be the reason to block it. But LLM generated code is not protected by law, and by extension you can damage your code base.
My company does not allow LLM generated code into anything that is their IP. Generic stuff outside of IP is fine, but every piece has to flagged that it is created by an LLM.
In short, these are just the next evolution of low quality PRs.
> 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.
> Everyone talking about having them break it down into smaller chunk. Vibe coding there is a near guarantee the person doesn't know what the code does either.
that's the point though, if they can't do it, then you close the ticket and tell them to fork off.
Copy and paste is your friend here. If there's 20+ huge PRs, just paste "This PR is far too large to review, please break it down and submit smaller PRs and engage with us ahead of time to understand how to solve this problem."
Comment & Close PR, only engage in discussions on tickets or smaller, understandable PRs.
As other have said: if someone drive-by opens a huge PR, it's as likely to be malware as a beneficial implementation.
> Vibe coding there is a near guarantee the person doesn't know what the code does either.
Having spent some time vibe coding over the weekend to try it out, I disagree. I understand every line of code the super-specific Android app I generated does, even if I don't have the Android dev experience to come up with the code from the top of my head. Laziness is as good a reason to vibe code as inexperience or incompetence.
I wouldn't throw LLM code at a project like this, though, especially not in a PR of this size.
That alone should be the reason to block it. But LLM generated code is not protected by law, and by extension you can damage your code base.
My company does not allow LLM generated code into anything that is their IP. Generic stuff outside of IP is fine, but every piece has to flagged that it is created by an LLM.
In short, these are just the next evolution of low quality PRs.