TEST_YOUR_KNOWLEDGE
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.
TEST_YOURSELF · How well do you know this science?
01 How many programmers participated in the 1968 Sackman/Grant study that is cited as the origin of the '10x programmer' claim?
McConnell's 2020 review traced the '10x' label to a 1968 study of just 12 professional programmers completing a single task. The ratio measured debugging time, not general productivity, and the small sample and single-task design were rarely flagged when the finding was subsequently cited. source ↗
02 What does the 'S' in the SPACE framework stand for?
Forsgren et al.'s SPACE framework stands for Satisfaction and wellbeing, Performance, Activity, Communication and collaboration, Efficiency and flow. Leading with satisfaction reflects the authors' argument that wellbeing is both a dimension of productivity and a necessary condition for the others. source ↗
03 According to Tulili, Capiluppi and Rastogi's systematic mapping study, what was the most consistently reported antecedent of burnout in software engineers?
Across 74 primary studies in the systematic mapping, overwork and high workload were the top antecedents of software engineer burnout. The review also identified engagement and autonomy as the most common protective factors — pointing away from 'work more' as a sustainable productivity strategy. source ↗
04 DORA's research on high-performing engineering teams measures four key metrics. Which combination is correct?
DORA's research established deployment frequency, lead time for changes, change failure rate, and time to restore service as the four key dimensions of software delivery performance. These metrics intentionally balance speed against reliability — teams maximizing speed alone at the cost of the other three consistently underperform on system-level throughput. source ↗
05 What did Murphy-Hill and colleagues find most strongly predicted individual developer performance at Google?
Murphy-Hill and colleagues found that team and organizational factors — including code review load, meeting culture, on-call burden, and psychological safety — predicted individual developer performance more strongly than individual effort or technical skills alone. This means two engineers of equal ability on different teams can show dramatically different output speeds for structural reasons. source ↗