Code as Culture How Organization Shapes Your Code
summary
Code reflects org structure: Conway’s law predicts a shared DB and monolithic API when 25 engineers are organized by function, so splitting into stream-aligned teams plus enabling, subsystem and platform teams produces separate infra, single-purpose databases, and three recommendation models each on its own pipeline. Team sizing matters (Dunbar 7–9, Spotify squads ≈6, Amazon two-pizza) and cognitive load drives communication paths. The recommended practice is a reverse Conway maneuver: design the desired architecture first, then create teams sized and tasked to produce it.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:40Why Code as Culture
- 1:50Organization Chart
- 2:12What is the Org Chart for
- 2:44What is it really for
- 4:11Think Team First
- 7:06Design an Organization Structure
- 10:22Conways Law
- 13:40Code First Thinking
- 20:27ORC Shard
- 22:00Architecture
- 27:39Org Chart
- 28:41Recap
- 30:42Questions
related talks
50mHow and why to design your Teams for modern Software Systems
31mHow and Why to Design Your Teams for Modern Software Systems
49mConway's Law: When Best Practices Are Not Enough
50mConway's Law: When Best Practices Are Not Enough
46mLeading Distributed Teams
08mWhy code describes business
56mTeams That Scale: Human Architecture for High-Performing Tech
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress