←back to thread

If you are good at code review, you will be good at using AI agents

(www.seangoedecke.com)
192 points imasl42 | 1 comments | 20 Sep 25 04:59 UTC | HN request time: 0.209s | source
Show context
rollulus ◴[20 Sep 25 09:50 UTC] No.45311885[source]▶
I have received a few LLM produced PRs from peers from adjacent teams, in good faith but not familiar with the project, and they increasingly infuriate me. They were all garbage, but there’s a great asymmetry: it costs my peers nothing to generate them, it costs me precious time to refute them. And what can I do really? Saying “it’s irreparable garbage because the syntax might be right but it’s conceptually nonsense” but that’s not the most constructive take.
replies(4): >>45311938 #>>45311960 #>>45312070 #>>45312146 #
1. tjpnz ◴[20 Sep 25 10:30 UTC] No.45312070[source]▶
If you had a colleague who was consistently writing complete shit you would raise it with your manager. This situation isn't all that different - the only complicating factor they're not on your team.

If it's only happened a few times you might first try setting some ground rules for contributions. Really common for innersource repos to have a CONTRIBUTING.md file or similar. Add a checkbox to your PR template that the dev has to check to indicate they've read it, then wait and see.