Developer Joy – How great teams get s%*t done
summary
Shows concrete changes at Atlassian: teams adopt coding guidelines and prewritten QA test plans, dedicate 10% time to developer productivity, and run demos and check‑ups tied to Compass/DORA metrics. A homebuilt flaky test detector auto‑retries and flags flaky tests, and a morning Punit bot cuts average PR review time from three days to 1.2 days. Results are measured, shared, and rolled out to other teams.
AI-written summary · about
chapters (15)
- 0:00Welcome
- 3:38Myth of productivity obsession
- 10:00Developer experience vs joy
- 12:30Technical debt drains joy
- 16:24Respectful code reviews
- 20:18Fixing flaky tests
- 23:48Speeding developer flow
- 27:39Autonomous teams analogy
- 30:53Quality assistance replaces QA
- 34:24Bridging product and dev
- 37:54Measuring joy with surveys
- 47:31Feelings over metrics
- 51:01Joy survey results
- 54:35Time for joy improvements
- 56:20Summary and call to action
related talks
48mDeveloper Joy – How Great Teams Get s%*t Done
58mDeveloper 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)
52mDeveloper Joy – How great teams get s%*t done
44mDeveloper Joy – How great teams get s%*t done
25mDeveloper Joy – How great teams get s%*t done
45mDeveloper Joy – How great teams get s%*t done