Coding Culture
summary
Claims concrete practices: Atlassian runs regular hack days that produce working prototypes and even a hidden Whiskey Bar built in 24 hours, and follows weekly demos plus fortnightly celebrations; an open‑source iPad happiness app tracks exit‑poll moods, Spotify raises reported happiness from 91% to 94%, team size targets sit at 6–8 with Dunbar ~150, and a Bitbucket Server add‑on autosuggest reviewers picks reviewers by file history. Culture scales via transparency, autonomy (“docracy”) and lightweight cross‑team sharing rather than heavyweight process.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:15What is culture
- 4:30Story time
- 9:30How Companies Motivate Innovation
- 12:35Innovation Days
- 22:30Happiness
- 30:10Dont write crappy code
- 31:43Find better ways
- 34:00Team size
- 38:06Bring people together
- 40:33Scaling
- 41:17Team Structure
- 43:05Democracy
related talks
43mKeynote: Coding Culture
49mHow-To: Build Thriving Cultures through Positive Communication
34mBuilding a Culture For Developer Productivity
32mCode First, Ask Questions Later
34mDeveloper First Culture
42mHealthy Teams, Healthy Code
19mTeam Culture: How the little things enable great outcomes
59m✊ Join the DEV-olution: A Culture of Empowered Developers