Lessons learned working remotely across timezones
summary
Fifteen months working across 6–9 time zones leads to concrete changes: introduces pull requests, dashboards and automation, and builds a separate CI that runs unit tests, PR builds and deploys to dev using Docker containers — but it never reaches production because the chosen SaaS build tool sits in a different cloud than corporate policy allows. Spins up about ten services without pipelines so the missing tracer bullet lesson surfaces, and finds self-service build pipelines and remote pairing with screen sharing actually work well.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 8:59Cultural shift in remote work
- 23:37Build servers and self-service challenges
- 34:02Productivity and team dynamics
- 45:23Slow query troubleshooting
- 49:45Key takeaways and Q&A
related talks
24mRemote development can improve your developers remote work experience
21mBuilding A DevOps Culture in a Remote World
43mOut of Sight, Out of Mind: Survival tricks and tools for remote developers
27mNavigating the Shift to Remote Developer Environments - A Year of Insights and Challenges
42mSustaining Remote – First Teams.
39mPerks and Pitfalls of Building a Remote First Team
40mBeing a remote developer
52mRemote Working Approaches That Worked (And Some That Didn’t)