Developer Joy – How Great Teams Get S%*t Done
summary
Software teams measure and improve developer experience with concrete changes: a flaky test monitor reruns failing tests, flags and skips >100 flaky tests last quarter, cutting wasted debugging time; a Punit bot replaces a morning nagger and drops PR cycle time from 3 days to 1.2 days while encouraging smaller PRs; teams allocate 10% developer Joy time to build tooling, set standards to fight technical debt (developers report ~42% of time spent on it, only 10% managed), and target >55% time changing the business.
AI-written summary · about
chapters (11)
- 0:00Why developer joy matters
- 3:54The productivity obsession
- 7:47Measuring developer productivity
- 13:26Fighting technical debt
- 20:13Fixing flaky tests
- 23:45Optimizing build and deploy
- 27:20Reducing wait time in reviews
- 34:26Aligning product and dev teams
- 41:36Five teams' joy strategies
- 48:58How to measure joy
- 55:44Turning signals into action
related talks
26mDeveloper Joy – How Great Teams Get s%*t Done
52mDeveloper Joy – How great teams get s%*t done
48mDeveloper Joy – How Great Teams Get s%*t Done
58mDeveloper Joy – How great teams get s%*t done
45mDeveloper Joy – How great teams get s%*t done
44mDeveloper Joy – How great teams get s%*t done
42mDeveloper Joy: How great teams get s%*t done
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)