Hacker News Reader

Comment by foxfired | Hacker News Reader

It's funny just today I published an article with the solution to this problem.

If they don't bother writing the code, why should you bother reading it? Use an LLM to review it, and eventually approve it. Then of course, wait for the customer to complain, and feed the complaint back to the LLM. /s

Large LLM generated PRs are not a solution. They just shift the problem to the next person in the chain.

View on HN

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.

The title says it is vibe-coded. By definition, it means they didn't write it.

But 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.

I'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.

You can recognize it by the rocket emojis in the PR description ;)

Then it would have extensive vcs history. Unless they just amend into one humongous commit.

Reply on news.ycombinator.com