Out of Sight, Out of Mind: Survival tricks and tools for remote developers
summary
Defines a remote-first workflow: test-driven development with unit tests and Selenium, GitLab pipelines that run CI on every commit, and Sentry + webhooks that push errors and deploy/status updates into chatbot-fed Slack so the channel is the project heartbeat. Teams use Skype or Google Docs for ceremonies, Docker/VMs and infrastructure-as-code for reproducible staging, and Trello/GitLab boards for planning. Keeps work moving and removes a single integration owner, but requires written working agreements (hours, availability, meeting cadence) and occasional in-person syncs to avoid constant interruptions.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 4:45Remote-friendly vs remote-first
- 8:42Agile and remote work
- 14:44Cultural shift in remote teams
- 17:38Team interactions and tools
- 28:42Q&A session
related talks
37mThe Effective Remote Developer
22mRemote Right: How to Thrive in a Post-Office World
42mSustaining Remote – First Teams.
31mAsynchronous Remote Work
27m"Thriving in a Connected World"
48mThe Remote Revolution
48mBuilding A Remote Engineering Culture
24mRemote development can improve your developers remote work experience