The Past, Present and Future of Developer Productivity Theories and Metrics
summary
Argues that measuring developer productivity needs concrete theory not just counts, using the SPACE framework (Satisfaction, Performance, Activity, Communication, Efficiency) to show dashboards over-index on activity/efficiency and under-report collaboration, well‑being and product quality. Gives a concrete claim: tools that add security guidance cut vulnerabilities and developer frustration while leaving deployment rate unchanged; a code‑review tool that reorders files lowers cognitive load and raises quality. Notes the developer portals goal: combine metrics, tooling discovery and community, and predicts AI will enable theory‑driven insights and self‑serve, role‑personalized dashboards (e.g., GET DX index, Cortex/Bridges experiments).
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 1:46Rise of developer portals
- 4:34History of developer productivity
- 7:45Theories and frameworks
- 15:15Theories of developer productivity
- 19:08What are frameworks
- 26:09Metrics and the SPACE framework
- 31:47Future of developer experience dashboards
- 37:07Q&A and closing remarks
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
11mWhat does 'productivity' actually mean for developers?
43mMeasuring Developer Productivity: The Good, the Bad and the Data
47mCan We Measure Developer Productivity?
26mWhere we’re going wrong with developer productivity
31mDeveloper productivity is waste
31mHow Do You Measure Devel...
37mA systems view of developer productivity