How Your Organization is Killing your Software
summary
Argument: massive rewrites usually cripple shipping — at Twitter a full-stack rewrite stops feature launches for about a year — so prefer incremental changes, not a single big-bang. Organizational shape follows Conway’s Law: move to small cross‑functional teams (recommendation teams of 3–7) and platform services (Twitter reached ~100 deploys/day after splitting into microservices). Practical tradeoffs include Ruby→Scala migration, region CDNs for latency, and accepting some duplicated tooling while reserving Sprint time for technical debt. Product needs a single decision‑maker to avoid consensus churn.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 5:37Why rewrites are dangerous
- 11:55Conway's law and team structure
- 20:22Microservices and team ownership
- 28:27Product dictatorship and simplicity
- 31:40Team culture and code
- 36:57Separating innovation from core teams
- 41:59Managing technical debt
- 46:07Architects vs agile teams
- 50:00Open source and team autonomy
related talks
45m"Moving Fast at Scale"
30mArchitecture & Teams at Less-than-Google Scale
01h 03mBeyond the innovator’s dilemma
47mGo Faster: Remove the Inhibitors to Innovation
41mThe big Rewrite
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
39mImplementing Programmer Anarchy
29mMoving Fast!