Keynote: Coding Culture
summary
Atlassian describes specific culture moves: quarterly 24‑hour hackathons called ShipIt that produce working prototypes (one used Google Translate), an iPad Mood App that captures daily happiness, and a Bitbucket add‑on suggested reviewers that chooses reviewers by file history. Teams target 6–8 people, coordinate across ~15 JIRA teams, and use autonomy + trust + transparency instead of heavy process. Engineering rules include “don’t write crappy code,” balance customer personas (Emma/William), and measure happiness frequently so problems surface and get fixed quickly.
AI-written summary · about
chapters (21)
- 0:00Introduction to coding culture
- 1:52Defining culture in organizations
- 3:39Perks vs. real culture
- 5:25Taylorism and modern work
- 7:50Culture changes over time
- 8:32Innovation in teams
- 10:20ShipIt Days and prototypes
- 13:07Celebrating team wins
- 16:39Cultural rock stars in support teams
- 18:31Measuring team happiness
- 20:44Passion and customer focus
- 24:21Engineering values matter
- 27:52Balancing passion and quality
- 28:35Team size and silos
- 30:18Transparency in organizations
- 32:25Scaling culture with autonomy
- 35:40Do-ocracy in teams
- 36:45Transparency in development
- 39:12Summary of key values
- 39:55Culture is alive and evolving
- 41:40Why culture matters most
related talks
49mCoding Culture
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)
58mKeynote: Seven Habits of a (Mostly) Successful Team
58mDeveloper Joy – How great teams get s%*t done
25mKeynote - From Code to Culture: Scaling Collaboration with InnerSource
34mBuilding a Culture For Developer Productivity
49mKeynote
01h 22mKeynote: Growing Better Programmers