Healthy Teams, Healthy Code
summary
Claim: team culture, not test coverage or tooling, most strongly predicts long-term code health and velocity. Internal Google research over a decade shows psychological safety trumps technical choices; teams that practice humility, respect and trust produce clearer proposals, better code reviews and fewer brittle tests. Concrete practices include kudos and the monkey ritual, blame‑free post‑mortems and peer bonuses (a 35‑person org shifts to ~one bonus a day). Expect individual output ~30–40 net LOC/week; collaborative teams ship more reliable systems.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:25Team culture matters most
- 2:55Programming education shapes behavior
- 6:48Programming vs software engineering
- 7:32Three pillars of teamwork
- 9:17Team culture impacts code and velocity
- 12:45Team cultures in code reviews
- 15:08Psychological safety with gratitude
- 16:10Practical steps for humility
- 17:34Respect as two-way relationship
- 20:48Trust through admitting mistakes
- 23:59Vulnerability strengthens bonds
- 24:41Culture roots engineering success
- 25:45Soft skills vs technical skills
- 26:29Q&A: Handling criticism
- 27:19Q&A: Toxic team members
- 31:08Q&A: Hiring for teamwork
- 32:55Q&A: Goal alignment
- 36:08Q&A: Formalizing failure rituals
- 41:23Closing remarks
related talks
47mThe Psychology of Software Teams
49mCoding Culture
46mProject Culture and Team Responsibility for Quality
36mPsychological Safety: Building fearless teams
22mPsychological safety: How to become a team that learns
38mImplementing a Strong Code-Review Culture
53mSwearing, Nudity and Other Vulnerable Positions
35mHealthy Teams: the practice behind the buzzword