Sustaining Remote – First Teams.
summary
TES runs a remote-first culture across ~50 engineers using homogeneous Node/React microservices, Docker/Kubernetes and VPNs, and insists all meetings default to video so distant people aren’t excluded. Remote pairing, recorded demos and two monthly hack days produce a static site generator for personal READMEs and Slack plugins that launch Zoom+Slack+ZenHub workflows. Office time drops to one week a year, commuting costs fall (one engineer cites ~£8,000 saved), and cross-team rituals plus mentoring make the approach practical and sustainable.
AI-written summary · about
chapters (39)
- 0:00Intro
- 1:10About Rachel Davies
- 2:33Show of hands
- 3:02A tale of woe
- 4:08Working from home
- 4:38Agile Manifesto
- 5:56Sitting Together
- 6:43Remote First Culture
- 7:23What does Remote First mean
- 8:51Tears Mission
- 9:20Engineers
- 9:52Connectivity
- 11:02Rules
- 11:16Meetings
- 13:19Office vs Shared House
- 15:44Quotes
- 17:10Working from home tips
- 17:45Tools we use
- 19:33Contact
- 21:12Pairing
- 22:39Setup
- 23:54Crossteam communication
- 25:22Hack days
- 25:34Personal profile
- 26:38Hacking
- 27:37Knowledge sharing
- 28:25Loneliness
- 29:54Other things people miss
- 30:54Combating loneliness
- 31:22Donut Buddy
- 32:05Remote Sharing
- 34:17Remote Conferences
- 34:50Engineering Week
- 35:13Remote Christmas Party
- 36:21Remote Rituals
- 38:12Promotion
- 39:36Business Benefits
- 40:44Rework
- 40:57Responsibility
related talks
13mManaging Remote Teams
30mEngineer's Lifecycle Management - Remote First Environment
39mPerks and Pitfalls of Building a Remote First Team
36mRemote work is here to stay: and what's next?
48mBuilding A Remote Engineering Culture
27mRemote Team Management
57mRemote Doesn’t Mean Distant - Managing Teams Effectively from Different Geographies
29mRemote(ly) Better Than Before