r/ProductManagement • u/ToLoveThemAll • 16h ago
Tools & Process PM contributing code with Opus 4.8 - realistic on a mature repo, or still a QA nightmare?
3-year-old codebase, 2 senior devs who are careful about best practices, security, testing. They're also equal partners in the company, so any efficiency gain lands directly in their pockets.
I'm a PM. I asked this same question ~9 months ago and the consensus was: reading/reviewing AI-generated code is harder than writing it, so my PRs would just be a tax on the senior devs. Not worth it.
Models and tooling have moved a lot since then. Honest gut check:
A. Is it reasonable now for a PM to open PRs with code written via Opus 4.8 (or better), on the condition that every contribution goes through heavy QA and testing before merge?
B. Any world where a PM pushes without a PR? Or is that still insane?
Where's the line in July 2026?
Edit:
People are asking why this is even a need. Two reasons: (a) the devs are slammed with other projects, and (b) the info gap between me and them creates a lot of back-and-forth, ping-pong, slow turnaround. On roles: we're all equal partners, so better process and faster results benefit everyone regardless of our traditional titles. And it goes both ways - the devs are free to push AI- or human-driven PM-side upgrades too, and they sometimes do.