← sources

Currently experiencing the nightmare of PMs pushing code

source: reddit (reddit:cscareerquestions)published 2026-10-29 21:13ingested 2026-10-30 02:36

retained text

It's hard enough to get some engineers on my team to understand the output of their AI when they throw up PRs now. But this is 10x worse when its non-engineers (PMs) doing so.

Today, I was auto-tagged in a PR that touched part of the codebase I'm a dedicated code owner for. An update to our team's owned code to make \[feature\] work for the +1k line PR. I wasn't reviewing that entire PR. I don't have time. I'll let the other team do it. At this point, with the amount of slop that goes through, its their problem if it breaks. But I'll be damned if its my teams code that causes issues. 

I treated our code changes like any other PR, and left the comments pointed out the issues.

The PM clearly just asked claude to "implement a fix" and pushed it back up, but this time with more issues, and then more commits came with additional feature changes, that added other issues.

I left comments, and the same happened. More slop on repeat loop.

The issue with a PM PR is that i literally cannot fucking reason with the author. They do not understand the diff. They dont understand the standards or why the comments are issues. So the feedback loop is just a meat proxy for me asking claude to fix it, but with a middle man who doesnt understand how to ask claude how to fix nor why.



document fetched 2026-10-30 00:23 · canonical https://reddit.com/r/cscareerquestions/comments/1xiwfay/currently_experiencing_the_nightmare_of_pms