> For the budding young developer who can't wait to show ideas to teammates and demonstrate being a go-getter by asking random questions and finding unaddressed

> For the budding young developer who can't wait to show ideas to teammates and demonstrate being a go-getter by asking random questions and finding unaddressed issues to innovate on, WFH might be terrible. You're going to schedule time to fortuitously run into the senior person who takes an interest in your idea? This doesn’t match my experience joining a fully distributed company straight out of college. I think, as always, this has much more to do with company culture. In distributed companies with strong communication cultures, it isn’t difficult to prove yourself a go-getter. There are easy avenues for asking lots of questions, and there are always lots of unsolved problems. In a culture which promotes learning and helpfulness, it’s easy to get an answer from a more experienced individual by pinging them directly. I would even suggest that if you have a strong async communication system on top of something like Slack, it is even easier to prove yourself than in person. Anyone and everyone has the ability to create posts and spark discussions which are very visible. You can, for example, write a post about a deep dive you did into X system, and post it for all devs to read internally. People will notice your efforts! This depends on having a great culture and good systems in place, of course. Many places don’t, which is why I think the focus ought to be more on remote culture and practices for distributed work.