Working Remotely as a Junior Developer
summary
Argues that juniors can work remotely though it’s harder and shows exactly how: negotiate by offering company benefits, prepare answers to common objections, and run a trial run (one week aligned hours then two weeks faking the destination timezone — three weeks total) to uncover problems. Uses Slack, Skype and GitHub pull requests for standups, code review and documentation. Outcome: processes improve, colleagues adopt occasional remote work and a US contractor gets hired, and the developer moves to Tokyo in October and works remotely for six months.
AI-written summary · about
chapters (7)
- 0:00Working Remotely as a Junior Developer
- 4:41Find benefits for the company
- 6:02Prepare to address their concerns
- 9:00Do a trial run
- 11:54Communicate proactively
- 13:20Document all the things
- 16:00Ask for pair programming, code reviews and feedback
related talks
28mHiring junior developers remotely
40mBeing a remote developer
01h 04mRemote Working for an Entrepreneur: Instructions for Use
45mThe Art of Remote
48mA 100% Remote Tech Team: It Works! / A 100% Remote Working Tech
47mExtreme Remoting
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
24m"Working remotely and how to scale a remote first environment"