Developer Joy – How Great Teams Get s%*t Done
summary
Argues that improving developer joy raises real productivity and gives concrete fixes: a flaky test detector that reruns failures, marks tests as skipped, comments on PRs and notifies Slack to stop half‑hour debugs; a Punit bot that pings reviewers each morning cutting average PR open time from 3 days to 1.2 days; shifting QA into quality assistance where devs do exploratory tests when QA ratio is 1:30; measures with DORA metrics and a Typeform developer joy survey and 10–20% time to fix tooling.
AI-written summary · about
chapters (14)
- 0:00Why developer joy matters
- 2:32Taylorism and productivity roots
- 4:37Measuring developer productivity
- 6:04Developer experience vs joy
- 7:48Code reviews and human side
- 10:16Flaky tests and frustration
- 12:43Optimizing development flow
- 14:27Autonomous teams and wait times
- 16:33QA as quality assistance
- 17:57Product and dev collaboration
- 19:44Measuring what matters
- 22:11Developer joy surveys
- 24:17Fixing and spreading improvements
- 25:41Summary and call to action
related talks
58mDeveloper 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
45mDeveloper Joy – How great teams get s%*t done
44mDeveloper Joy – How great teams get s%*t done
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)
25mDeveloper Joy – How great teams get s%*t done
33mMeasuring Developer Productivity: the good, the bad and the data