The Good, The Bad and the Ugly - Building Distributed Teams at Realm
summary
Realm runs ~50 employees with about one third remote and teams spanning 17 time zones. Communication uses Slack (fine‑grained, ~200 channels, force threads), GitHub (small PRs, work-in-progress PRs, squash merges), Zoom for video and Google Docs for live prototyping. Processes that work: daily 2‑minute async standups aggregated to weekly status, optimistic approvals to shorten review cycles, a single required weekly team meeting, assigned feature leads to unblock decisions. Pain points: long turnaround, tool choice mismatches, and the need for a few hours of overlap.
AI-written summary · about
chapters (10)
- 0:00Introduction to distributed teams
- 3:16Team distribution challenges
- 6:08Asynchronous communication essentials
- 9:37Efficient code reviews remotely
- 12:03Tool selection and usage
- 17:01Slack best practices
- 23:42Managing notifications and work hours
- 26:14Decision-making in remote teams
- 33:17Social interaction and team bonding
- 38:13Key learnings and takeaways
