The Outdated Obsession with Lines of Code
For decades, engineering organizations have fallen into the same trap: measuring developer productivity by the volume of code they produce. Lines of code (LOC) feels tangible. It feels measurable. And it feels completely wrong.
A developer who refactors 500 lines into 50 hasn’t been unproductive — they’ve made the system dramatically better. A senior engineer who spends a week mentoring teammates and designing architecture may commit nothing at all, yet their impact reverberates for months.
Lines of code measure activity. DORA metrics measure outcomes.
What DORA Metrics Actually Tell You
The four DORA metrics — established through years of research by the DevOps Research and Assessment team — focus on what truly matters: how effectively your team delivers value to users.
- Deployment Frequency — How often are you shipping to production? Teams that deploy frequently tend to ship smaller, safer changes.
- Lead Time for Changes — How long does it take for a commit to reach production? Shorter lead times mean faster feedback loops and quicker value delivery.
- Change Failure Rate — What percentage of deployments cause failures? This measures the quality of your delivery pipeline, not just its speed.
- Mean Time to Recovery (MTTR) — When things break, how fast do you bounce back? Resilience matters more than perfection.
Together, these metrics paint a picture of a team’s delivery capability — something no line counter could ever capture.
The Danger of Vanity Metrics
When you measure lines of code, you incentivize the wrong behaviors:
- Code bloat — Developers write verbose solutions instead of elegant ones
- Copy-paste culture — Why write a reusable function when duplication inflates your numbers?
- Fear of deletion — Removing dead code becomes a productivity penalty
- Individual competition — Collaboration suffers when everyone is chasing personal output numbers
DORA metrics flip this entirely. They’re team-level signals that encourage collaboration, shared ownership, and continuous improvement. Nobody games deployment frequency by shipping broken code — because change failure rate keeps that in check.
Measuring What Matters
The shift from LOC to DORA metrics isn’t just a tooling change — it’s a cultural transformation. It tells your team: We care about the software you deliver, not the keystrokes you type.
Elite-performing teams, according to the State of DevOps research, deploy on demand, with lead times under a day, change failure rates under 5%, and recovery times under an hour. None of those benchmarks mention a single line of code.
Start measuring what matters. Your teams — and your users — will thank you.