Developer Joy – How great teams get s%*t done
summary
Teams report concrete wins: a morning Punit bot reminder cuts average PR time from three days to 1.2 days; a homegrown flaky-test detector reruns and auto-skips tests, surfacing 15 flaky tests across 10 teams and saving many engineering hours; a QA “quality assistance” model shifts testing responsibility to developers with QA-led kickoffs (QA:dev ratio was 1:30); policy sets 55% time for new features, 35% for keeping lights on and 10% for tooling/improvement (55/35/10), plus a monthly developer-joy survey driving team-level fixes.
AI-written summary · about
chapters (18)
- 0:00Why developer joy matters
- 3:13From productivity to joy
- 7:12Why old metrics fail
- 10:25Developer joy defined
- 13:57Better code reviews
- 16:09Fixing flaky tests
- 20:03Build test deploy optimization
- 23:55Reducing team friction
- 27:07Quality assistance
- 30:20Better collaboration with product managers
- 36:03Effective demos
- 38:29Measuring DX with DORA
- 41:18Feature vs maintenance balance
- 44:26What devs really need
- 45:55Developer challenge poll
- 48:49Running DX surveys
- 50:37Empowering teams
- 51:18Code progress and value
related talks
58mDeveloper Joy – How Great Teams Get S%*t Done
26mDeveloper Joy – How Great Teams Get s%*t Done
25mDeveloper 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
42mDeveloper 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