There are no snow days when you work remote
summary
Argues remote work succeeds only when the company provides explicit support: a documented onboarding with equipment, contact list and tools (Slack, Zoom, GitHub), meetings with join links and timezone-aware scheduling, and always-available task management (JIRA/Trello/GitHub issues) with clear requirements and completion steps. Demands documentation for environments, builds and tests because slack does not equal documentation. Rejects “butt-in-chair” metrics; favors outcome-based reviews. Advises personal rules: set office hours, take breaks, avoid chores during work, and cultivate community via coworking, meetups or mentoring.
AI-written summary · about
chapters (14)
- 0:00Intro
- 4:12THE REMOTE COMPANY CHECKLIST
- 8:08HAVE MEETINGS BUILT TO BE INCLUSIVE OF REMOTE WORKERS
- 15:25COMMUNICATION CONSIDERATIONS How is comparty-wide information relayed?
- 20:23THERE SHOULD BE DOCUMENTATION AROUND
- 23:50EVALUATION SYSTEMS IN PLACE
- 24:42EVALUATION CONSIDERATIONS
- 27:06IS WORKING REMOTE THE RIGHT FIT FOR YOU?
- 32:56ESTABLISH & MAINTAIN BOUNDARIES
- 38:06TRAP: SLACK, SOCIAL MEDIA, AND OTHER DISTRACTIONS
- 39:23CREATE A PRODUCTIVE ENVIRONMENT
- 40:38FOLLOW A DRESS CODE
- 41:52BE "VISIBLE" IN THE COMPANY
- 45:31ENGAGE WITH YOUR LOCAL TECH COMMUNITY
related talks
55mThere are no snow days when you work remote.
44mThere are No Snow Days When You Work Remote
54mEffective Remote Teamwork
52mRemote Working Approaches That Worked (And Some That Didn’t)
36mThings I Wish I Knew Before Going Remote
45mThe Art of Remote
40mBeing a remote developer
36mWorking Effectively Across Space-Time