Developer Joy – How great teams get s%*t done ( Closing Keynote)
summary
Teams at Atlassian measure and fix concrete blockers: a bot cuts pull‑request latency from 3 days to 1.2 days, a flaky test detector reruns failures, comments and auto‑skips flaky tests, and a code‑review etiquette (assume competence, be constructive, explain reasoning) reduces bullying. DORA metrics and a Developer Joy survey produce an opportunity score; org policy grants 10% time for developer‑experience work and tracks time spent on “change the business” versus keeping the lights on.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:26Changing role of developers
- 3:38Origin of productivity obsession
- 6:31Why metrics fail developers
- 8:40Developer experience vs joy
- 10:25Better code reviews
- 15:04Fixing flaky tests
- 18:42Optimizing build flows
- 21:48Autonomous teams
- 24:59Cross-functional teams
- 28:35Product-dev collaboration
- 31:47Product phases and demos
- 35:43Measuring developer experience
- 38:35DORA metrics
- 41:23Developer Joy survey
- 44:36Fixing challenges with 10% time
- 46:22Sharing learnings
- 47:48Where joy happens
- 48:11Closing remarks
related talks
58mDeveloper Joy – How great teams get s%*t done
45mDeveloper Joy – How great teams get s%*t done
26mDeveloper 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
44mDeveloper Joy – How great teams get s%*t done
52mDeveloper Joy – How great teams get s%*t done
25mDeveloper Joy – How great teams get s%*t done