3 ms·
How do you know they didn't bother to write it? For all we know the submitter has been quietly hammering away at this for months.
by throwawayffffas 1y ago
How do you know they didn't bother to write it? For all we know the submitter has been quietly hammering away at this for months.
- foxfired 1y agoThe title says it is vibe-coded. By definition, it means they didn't write it.
- throwawayffffas 1y agoBut how do they know it's vibe-coded? It may have a smell to it. But the author might not know it for a fact. The fact it's vibe-coded is actually irrelevant the size of the request is the main issue.
- foxfired 1y agoI'm not gonna make assumptions on behalf of OP, but if you have domain knowledge, you can quickly tell when a PR is vibe-coded. In a real world scenario, it would be pretty rare for someone to generate this much code in a single PR. And if they did in fact spend 6 months painstakingly building it, it wouldn't hurt to break it down into multiple PRs. There is just so much room for error reviewing such a giant PR.
- sunaookami 1y agoYou can recognize it by the rocket emojis in the PR description ;)
- deleted 1y ago[deleted]
- wiseowise 1y agoThen it would have extensive vcs history. Unless they just amend into one humongous commit.