Measuring Engineering Productivity | Off by One
A lightweight system for measuring engineering productivity that puts the overhead on managers, not engineers—using changelogs, standups, and visibility over surveillance
Engineers love to measure things: latency, throughput, error rates. But try to measure their own work? Then metrics become the enemy. I get it. I’ve seen enough terrible systems to understand the resistance. Most systems fail, thanks to Goodhart’s Law . Measure the lines of code written, and people jack up verbosity. Measure the number of PRs, and people start dividing up their PRs. Yet, it all feels like you have to measure something . Every manager knows that some people are more productive than others. Clearly, there’s a way to ascertain productivity. And even a given individual has their e
Explore this link on the map →related reading
- Measuring an engineering organization. | Irrational Exuberancelethain.com
- claude code is not making your product betterethanding.substack.com
- Legal AI Blog for Law Firms | Guides, Reviews & Insights — Augustaugust.law
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Estimating the Productivity of an Autonomous AI Software Engineer | Cognitioncognition.ai
- 2× - by Darragh Curran - Fin Ideasideas.fin.ai
- rotorlab.tamu.edu/me489/README/2010 ASME Unwritten_Laws_of_Enginering.pdfrotorlab.tamu.edu
- Why I Ignore The Spotlight as a Staff Engineer - Lalit Magantilalitm.com
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Infrastructure Gravity & Domain Engineering | Jack Dangerjackdanger.com
- How Linear builds product - by Lenny Rachitskylennysnewsletter.com
- Atlassian Engineering's handbook: a guide for autonomous teams - Inside Atlassianatlassian.com