Developer Joy – How great teams get s%*t done
summary
Claims concrete wins: PR wait time falls from three days to 1.2 days after adding a morning ping bot (Punit bot) and smaller pull requests, code review etiquette enforces assume competence, be constructive, explain reasoning, QA shifts to developers with QA kickoffs and QA becoming “quality assistance” to handle a 1:30 QA:dev ratio, metrics live in Compass scorecards with a tracked 45% new features vs 35% upkeep split and a 10% improvement budget, and GitHub’s Good Day finds no simple correlation between feelings and activity metrics.
AI-written summary · about
chapters (15)
- 0:00Joy of coding
- 1:57Cognitive load rise
- 2:41Taylorism myths
- 4:06Wrong productivity measures
- 5:30Developer experience over frameworks
- 6:55Fixing code review culture
- 10:03Optimizing pipelines for flow
- 12:30Autonomous teams without QA bottlenecks
- 15:18Measuring dev experience with DORA
- 17:46Balancing change and maintenance
- 19:31Ask developers what matters
- 21:58Surveys for improvements
- 22:4010% time for dev experience
- 23:23Spreading improvements
- 24:04Developer joy equals productivity
related talks
52mDeveloper Joy – How great teams get s%*t done
26mDeveloper Joy – How Great Teams Get s%*t Done
58mDeveloper Joy – How Great Teams Get S%*t Done
58mDeveloper 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
42mDeveloper Joy: How great teams get s%*t done
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)