Being a remote developer
summary
Remote work broadens hiring and lets teams hire rare talent across borders but creates real gaps in gossip, launches and onboarding; fixes that worked include 3-week onboarding in Helsinki and 2-week onboarding in Amsterdam, renting a small shared office with friends, and using HipChat, Slack, Zoom and Google Hangouts for pair programming and screen sharing. Specific practices that matter: daily standups, weekly retrospectives, explicit status messages, agreed work hours and async signals. Cautionary claims: avoid putting juniors or people switching languages into remote roles.
AI-written summary · about
chapters (35)
- 0:00Intro
- 1:01DREAM JOB AHEAD
- 3:17WHY COMPANIES HIRE REMOTES?
- 4:40CULTURAL DIVERSITY
- 5:19FINDING RARE TALENT
- 6:11MY STORY
- 6:23ACCELERATOR
- 6:57ACCELLERATOR ENDED
- 7:10THIS IS HOW I BECAME A REMOTE DEVELOPER
- 7:50HOURS / DAY
- 8:32ISOLATED
- 8:52FRIENDS
- 10:20FIND WORK-LIFE BALANCE
- 11:36REMOTE E FREELANCING
- 12:23NOT PART OF A TEAM
- 13:29KEEP COMMUNICATING
- 13:45PEOPLE LEFT
- 14:09DEADLINE MOVED UP
- 14:24ROADMAP CHANGED
- 16:23DAILY STANDUPS
- 17:40SCREEN PAIR PROGRAMMING
- 18:10TEAM RETREATS
- 19:08TIPS
- 20:17TEAM MEMBERS FROM AROUND THE WORLD
- 20:58PASSIONE AGGRESSION
- 21:44F WORD BOMB
- 23:34MOTIVATED
- 24:03TRACK YOUR TIME
- 24:55WITH FREEDOM COMES RESPONSABILITY
- 26:19COMMUNICATE ON/OFF
- 26:48GOOD MORNING
- 26:59NOT FOR EVERYONE
- 27:28TRUST
- 29:14DAY A WEEK
- 29:241 DAY A MONTH
related talks
22mWorking Remotely as a Junior Developer
48mThe Remote Revolution
29mRemote(ly) Better Than Before
45mThe Art of Remote
28mHiring junior developers remotely
30mEngineer's Lifecycle Management - Remote First Environment
36mRemote work is here to stay: and what's next?
39mPerks and Pitfalls of Building a Remote First Team