Developer Joy – How great teams get s%*t done
summary
History of Taylorism frames the problem and the talk prescribes concrete fixes: start with DORA metrics and Compass, measure developer joy with a survey that yields opportunity scores, address 40% of developer time lost to technical debt, run weekly checkups, and carve out developer Joy weeks. Teams build a flaky test detector that reruns and annotates failures and a Punit bot that cuts PR review time from three days to 1.2 days.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:47Productivity obsession history
- 6:03Developer productivity pitfalls
- 8:29Developer experience to joy
- 10:16Code quality and technical debt
- 13:30Kind code reviews
- 16:38Fixing flaky tests
- 19:28Dora metrics and baselines
- 21:12Developer flow and review time
- 24:45Autonomous teams analogy
- 27:55Quality assistance replacing QA
- 30:00Collaborating with product teams
- 34:11Celebrating progress
- 34:32Measuring developer joy
- 39:04Developer Joy survey actions
- 40:51Summary
related talks
26mDeveloper Joy – How Great Teams Get s%*t Done
45mDeveloper 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
52mDeveloper Joy – How great teams get s%*t done
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)
58mDeveloper Joy – How great teams get s%*t done
42mDeveloper Joy: How great teams get s%*t done