Building Distributed Systems in Distributed Teams
summary
Company runs distributed by design with core tools: lots of email, Slack and Zoom for sync and something like Git for async, regular all-hands that scale to hundreds. Policy favors trust and autonomy: no time tracking, people set boundaries, “do the right thing” and accept occasional failure. Pain points are real: heavy time-zone friction across Australia, China, India, Europe and US, frequent written miscommunication that requires hopping on video, and the blunt metric shown — about 40–50 hires/month with a recent three‑month snapshot of 130 joins and 9 leaves.
AI-written summary · about
related talks
23mBuilding Distributed Systems in Distributed Teams
47mDistributed - of Systems & Teams
41mThe Good, The Bad and the Ugly - Building Distributed Teams at Realm
07mOutlines the Risks Surrounding Distributed Systems
11mSS & BR: Building Distributed Systems in Distributed Teams
44mDistributed journey
19mEngineering for the Long Game
33mWhy Are Distributed Systems So Hard?