Developer Joy: How great teams get s%*t done
summary
Confluence teams build a flaky test detector that reruns a failing test up to four times, auto-marks flakes as skipped, leaves a PR comment and sends a Slack alert, which cuts debugging frustration. Reviewer pings get automated by the Punit bot, dropping median PR time from three days to 1.2 days. QA becomes quality assistance when one QA supports ~30 devs via QA kickoffs and test plans. Compass and DORA-style metrics plus regular developer-joy surveys and 10% time for fixes track and fund concrete improvements.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:56Development has changed
- 5:40How to measure developer productivity
- 12:10Why I dont like code reviews
- 12:30Code reviews rules
- 19:00Punit Aurora
- 20:36Traffic Junction
- 22:54Autonomous Teams
- 25:01QA Kickoff
- 26:06Do we have the same language
- 28:35Make phase
- 32:03Developer Joy
- 35:24Measuring developer productivity
- 37:25Vital Signs
- 38:28Opportunity Score
related talks
58mDeveloper Joy – How great teams get s%*t done
52mDeveloper 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
25mDeveloper Joy – How great teams get s%*t done
44mDeveloper Joy – How great teams get s%*t done
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)
45mDeveloper Joy – How great teams get s%*t done