CTO Tracks PRs Per Engineer as AI Productivity Metric — PRs Doubled but Reverts Jumped to 23
Few-Pilot7575 · reddit · 2026-11-20
- Setup: After a CTO bought coding agents for all 40 engineers last summer, finance demanded proof of ROI and picked "PRs merged per engineer per week" as the metric. It rose from 3 to nearly 6.
- Hidden problems: Agents split work into many tiny PRs, inflating the number; reverts jumped from 9 to 23 last quarter; the two most senior engineers now spend most of their week reviewing instead of building — none of this shows in "PRs per engineer".
- Suggested companion metrics: monthly reverts/hotfixes, time from PR opened to merged, review comments per PR (AI + human), and PRs re-touching the same files within two weeks. The manager liked it; the CTO called it "too many numbers".
- Takeaway: No single number tells the truth about agent productivity; you need a small set of complementary metrics.
More from coding & agent
- Mubit + Neon: agent middleware cuts frontier-model tokens by 73% — JeremyCMorgan · 2026-11-20
- Uber's Legal AI Agent Cuts Contract Review Time by 20% with 91% Accuracy Using RAG and Rules — nilukush · 2026-11-20
- Open-source MCP server gives your ChatGPT or Claude an A2A address so AIs can haggle with each other — IDforOpus · 2026-11-20
- The hardest work skill by 2028 won't be prompting — it's writing goals you can accept — evisoft · 2026-11-20
- Claude autonomously plays Taiko Web on a user's machine and hits a full combo — ezshine · 2026-11-20
- px0: A 20MB browser-based IDE for AI-generated code, built by chopping layers with first-principles thinking — arpit_bhayani · 2026-11-20