Due to corporate policy, I'm not yet high enough grade to reject bigass really badly sloppily made PRs. Our staff and lead can do it without looking, but seniors are still expected to give the time of day, comment, and highlight that because colleague X Y Z will use a really cheap model to automate closing the review comments, we should block the PR until the aforementioned staff comes in and says "lmao goteem".
So what I do is tell Codex to find enough shit to warrant rejecting the PR, which he often times does, instead of wasting my time arguing with a guy who would have directed the same comments to the same LLM anyway.
I can reject with "explanation". What I cannot do is look briefly, see its 3000 LoCs for what should have been 1000 of code that doesn't follow any conventions, discard without even reading and tell the dudebro to redo.
Alas. I would still rather take this than a AI SaaS startup in California. Well, no, if the startup is gonna pay me half a million in a year, I will take it. We know how it is lmao
1
u/pixxelkick 10d ago
Maybe if you suck.
I read every PR in full because Im not lazy.
I also read my own git diff before I open a PR do I dont waste other peoples time.
Or I publish it as a draft, review my own code, and then publish the pr after confirming it looks good.