REALITYWIPE

BY_THE_NUMBERS

The Science of Engineering Pace: Why Comparing Velocity Is the Wrong Metric

"She ships twice as fast as me — I must not be cut out for this" is the kind of thought software engineers rehearse constantly, usually at 11pm staring at a half-finished PR. What the research shows is that this comparison rests on shaky foundations. The original '10x programmer' finding came from 12 people in a 1968 study that measured time-on-task for a single assignment, under conditions that have little resemblance to modern software work. Half a century later, the SPACE framework documented that developer productivity is multidimensional — speed is one slice of a much larger picture, and the other slices are often invisible in peer comparisons. Meanwhile, a systematic mapping of the burnout literature established that chronic overwork is a reliable predictor of engineer burnout, not a sign of exceptional dedication. The old script — 'work faster, prove your worth' — is at odds with what the evidence shows about how good engineering actually gets done.

12programmers in the 1968 Sackman/Grant study that gave rise to the '10x' myth — the entire origin of a half-century-old folk belief about software developer productivity5 dimensionsthe SPACE framework's count of independent developer productivity dimensions — Satisfaction, Performance, Activity, Communication/collaboration, Efficiency/flow — none of which can be fully captured by velocity alone74 studiesprimary studies synthesized in Tulili et al.'s 2022 systematic mapping of burnout in software engineering, where overwork and high workload consistently top the list of burnout antecedents4 DORA metricsthe four-dimensional engineering performance model used by DORA research (deployment frequency, lead time, change failure rate, time to restore) — teams optimizing on just one dimension at the expense of others consistently underperform on system-level throughput
View full research filetest your knowledgeAll research