The Definitive Answer to Measuring Developer Productivity
summary
Claims a research‑backed system can measure real coding skill by running five tasks in a real IDE on a proxied VM, using time and quality metrics plus models like Dunning‑Kruger and RUSH. The project gets ~€500k funding, boots a multinational control group, and produces per‑area scores (object orientation, unit tests, coding speed). Demo shows partly automated grading, manual review for edge cases, and a hiring rule of score <4 filter, >6 strong hire, now being trialed for Foojay.io Java certification.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:41Developer productivity research
- 13:47Dreyfus model explained
- 21:56Skill measurement research
- 28:38Reps platform demo
- 33:40Java certification proposal
- 37:09Q&A
related talks
43mMeasuring Developer Productivity: The Good, the Bad and the Data
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
27mDevelopers Expose What's Breaking Productivity in Their Companies
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
31mDeveloper productivity is waste
02h 31mDeveloper Productivity Engineering - Extended Session
01h 00mWhat We Mean When We Talk About Developer Productivity
36mDeveloper Productivity Engineering: What's in it for me?