Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm glad I'm not the only one who gets viscerally irritated when I'm asked to review a PR that was obviously generated. You didn't take the time to write this code, but you expect me to take the time make sure it's correct, which will take far longer than a regular PR because there's no reason to assume an LLM even understood the task. Next time just be honest and ask me to do your work for you.


> You didn't take the time to write this code, but you expect me to take the time make sure it's correct

So, I guess there are a couple parts here right? I might not take the time to write the code, but surely I am on the hook to demonstrate that I've tested the code or have very good reason to believe it's correct?

If people are pushing PRs [of any meaningful complexity] without knowing whether they work in the general case that sounds like a failure of process and/or training. For me PRs are about catching edges?


I'll quote from my parent comment:

> somebody asking you to review something they haven't even looked at

The situation you're talking about is not the one we're talking about, so I'm not sure what you're taking issue with.


My boss decided to start putting out a ton of PRs from Devin at one point. I told him I'm spending more time reviewing his PRs than he was saving.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: