Developer Joy – How great teams get s% t done
summary
Shows concrete Atlassian fixes: an internal flaky test detector that reruns failures, marks flakes, comments PRs and alerts Slack to save ~15 minutes per incident; a Punit bot that pings reviewers and cuts PR lead time from three days to 1.2 days; a QA kickoff pattern that shifts responsibility to teams; a metrics stack (DORA-like plus Compass) and time budget of 55% change the business / 35% keep the lights on / 10% developer joy; and demo videos on Loom yielding 50% more engagement than live calls.
AI-written summary · about
chapters (11)
- 0:00🚀 Introduction: What is Developer Joy?
- 3:30The Evolution of Developer Roles and Responsibilities in the Last Decade
- 7:00The Impact of Cloud, Microservices, and Containers on Developer Work
- 12:00The Productivity Dilemma: From Factory Models to Developer Experience
- 17:00The Importance of Developer Joy in Enhancing Productivity
- 20:00How to Foster Developer Joy Through Quality Code and Fast Progress
- 25:00Creating a Positive Feedback Culture in Code Reviews
- 30:00Handling Flaky Tests and Optimizing Development Pipelines
- 35:00Enhancing Flow Between Teams and Minimizing Friction
- 40:00Using Metrics to Measure Developer Joy and Satisfaction
- 43:00Conclusion: How Developer Joy Leads to Sustainable Success
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
30mReal-Life Tips on How to Boost Your Development Team's Productivity from Within
52mProductivity is Messing Around and Having Fun
01h 01mDeveloper Happiness and Why it Matters
48mThe Effective Software Architect - Work Smarter, not Harder
17mCreating Happy Engineers - Anecdotes from the Trenches
49mCoding Culture
34mDeveloper First Culture