Distributed Sys Teams
summary
Advocates hiring worldwide and treating people like distributed infrastructure, citing eight years remote experience and Fastly’s 65 points of presence (Mar 31 2019) as context. Recommends concrete practices: prefer email for asynchronous decisions, use Slack/Zoom/Google Hangouts/FaceTime for sync, over-communicate intent, document alongside code, publish status updates as async standups, offer flex hours, schedule at least one weekly full-team meeting, and rely on global handoffs (example: a multi-continent incident response that kept coverage without waking anyone at 3 AM).
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 1:32Company and agenda
- 1:53Distributed systems
- 3:35The case for global talent
- 5:09Selecting tools
- 6:40Communication strategies
- 7:34Cultural considerations
- 8:40Empathy in the workplace
- 9:16Building team bonds
- 13:02Understanding privilege
- 14:08Benefits and conclusion
- 15:29Q&A session
related talks
47mDistributed - of Systems & Teams
13mManaging Remote Teams
08mHow to run distributed teams
37mBuilding & Scaling Distributed Teams
33mTips for Managing a Widely Distributed Team
33mDistributed Teams
57mLessons from {distributed,remote,virtual} communities and companies
31mThe art of distributed work: Harnessing strengths & mitigating weaknesses for asynchronous success