Distributed - of Systems & Teams
summary
Advocates building teams remote-first not as an afterthought, with explicit practices: put AWS CloudFormation/Terraform JSON in GitHub, use a Jenkins job that breaks the build if infra changes, write rich commit messages and meeting notes, and prefer durable communication over ephemeral calls. Treat partitions as time-bounded and decentralize decision-making so local sites don't wait on HQ. Plan human redundancy (cross-train backups), onboard people in person briefly, and use Slack/Docs/GitHub presence to reduce coordination surprise.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 2:12Distributed teams
- 3:31DevOps
- 5:58Empathy
- 8:14Nonviolent Communication
- 10:02Common Ground Paper
- 11:40Documentation
- 13:12Writing down problems
- 14:40Durable communication
- 15:52Partitions
- 16:36Target
- 18:11Microservices
- 19:52Continuous partial failure
- 21:56Microservices teams
- 23:17Conways Law
- 24:47Tools
- 25:10Synchronous communication
- 26:30Inperson onboarding
- 27:37Call Me Maybe
- 28:34Dramafever
- 32:45Moving to San Francisco
- 34:13Industry change
- 35:17Talent shortage
- 36:30Flexibility
- 37:26Remote vs Colocated
- 40:51Interacting with Others
- 42:59Wrap Up
- 43:09Questions
related talks
38mDistributed Sys Teams
05mBuilding Distributed Systems in Distributed Teams
08mHow to run distributed teams
13mManaging Remote Teams
01h 06mLeading successful remote teams
57mLessons from {distributed,remote,virtual} communities and companies
37mBuilding & Scaling Distributed Teams
39mPerks and Pitfalls of Building a Remote First Team