Disclaimer: I've never worked from home. I have thought about it a lot though.
I think WFH isn't a good idea for a junior dev (e.g., <5 yrs experience). In my career, I've learned the most from working closely with really smart engineers, and doing CRs over email isn't sufficient to soak up that knowledge. Standing at a whiteboard and arguing about design patterns for an hour, sitting at the same computer crafting a new API, etc., are the best ways for you to learn quickly.
It's also important that you work on a team with smart engineers for the above to be valuable. If you have no CR process, or don't have any devs smarter than you, then there aren't any downsides to WFH, but that's only because the above upsides aren't there.
Comments
Disclaimer: I've never worked from home. I have thought about it a lot though.
I think WFH isn't a good idea for a junior dev (e.g., <5 yrs experience). In my career, I've learned the most from working closely with really smart engineers, and doing CRs over email isn't sufficient to soak up that knowledge. Standing at a whiteboard and arguing about design patterns for an hour, sitting at the same computer crafting a new API, etc., are the best ways for you to learn quickly.
It's also important that you work on a team with smart engineers for the above to be valuable. If you have no CR process, or don't have any devs smarter than you, then there aren't any downsides to WFH, but that's only because the above upsides aren't there.