The Effective Remote Developer
summary
Practical rules for doing remote development: adopt the four mindsets — communicate frequently and clearly, be responsive but set boundaries, assume good intentions, help others help you — and use concrete habits: break work into small pull requests on GitHub, screencast demos with Jing, sketch diagrams in OmniGraffle, use a decent mic (even Apple earbuds), run a company-wide video system (WebEx works), and keep regular in-person meetups (engineering meets every three months). At Stitch Fix over 70 engineers work remotely and over half the engineers live outside the Bay Area, so these practices scale.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:224+ Years Remote
- 2:42What Is "Effective"?
- 7:06Four Mindsets To Build & Maintain Trust
- 13:23Be Responsive, But Set Boundaries
- 22:28Assume Good Intentions
- 29:49Help Others Help You
related talks
44mThe Keys to Working Remotely
43mOut of Sight, Out of Mind: Survival tricks and tools for remote developers
56mMental Health and Working Remote
27m"Thriving in a Connected World"
35mPair Programming from 2,000 km Away: Strategies for Distributed Agile Teams
24mRemote development can improve your developers remote work experience
45mOptimizing remote work: Pull Requests, Stand-ups, and emojis with Kasey Kelly
46mHome Alone: How working for a fully remote company actually works