Hacker News new | ask | show | jobs
by rollulus 24 days ago
I’m in the very same situation currently. A coworker vibe coded a PR for me to review. I asked: normally I would ask “why did you do xyz”, but what are you going to do now, proxy that question to your LLM? And is the LLM going to construct a “why” based on the nonsensical code it produced? Is this how we want to work?

The review is currently stalled in absence of answers.
3 comments
phendrenad2 24 days ago
> what are you going to do now

You're going to ask your own LLM session why they did it that way. And if there's a problem, you raise it. And if this individual keeps opening buggy PRs, you have a talk with them about how to use the LLM to catch these issues before a PR is opened.

link
Jianghong94 24 days ago
Seriously, it's much easier to review the AI generated plan, instead of reviewing their code. What I found is that, if the change surface is small enough, AI can get it right under the correct assumptions, but the noob mistake is to let AI loose and come up with its own, often not correct assumptions. So you got to step in before they generate the whole slop...
link
AuthAuth 23 days ago
talk to them and ask the question or call and ask?
link