> and this is especially true if some of the team members are young and inexperienced I think this is the big one for me, at least with the experience of WFH f

> and this is especially true if some of the team members are young and inexperienced I think this is the big one for me, at least with the experience of WFH for Covid, it is so much harder for people to ramp up and learn in a WFH situation, you can't just ask your neighbor about a weird compile issue, or why the IDE isn't able to run your tests and be helped promptly with them just showing you right away. Instead you ask in a Slack, get a slow churn of reponse, nothing helpful enough, so you then schedule an actual short meeting with someone else to walk you over it, etc. And this support doesn't naturally distribute like it would at the office, it seems it's always the same more senior person remotely who has to now help new members in these more formal ways. I've also seen so much more just confusion around like, what to do, who's doing what, when to do it, etc. Getting everyone aligned and in-sync is much harder. And that adds a lot of overhead and creates a lot more churn I feel to projects. On the flip side, when you have a clear task to do and you know what needs to be done and it doesn't depend on others, you can really crush through it. And you save a lot of time from commute, launches are faster, etc. I've also found, appart from Covid, remote work is pretty nice in terms of work/life balance. You can make laundry while you work for example, saving you time in your day. So I'm still a bit mixed feelings about WFH, I like some aspect of it, mostly no commute, convenience of being at home so I can easily cook my launches at launch time, do some laundry or have the oven repair person show up and manage them while I work and all that. But I also feel doing the actual day to day work is harder, the coordination overhead is pretty high, and everyone is more siloed, so anything that involves collaboration has more friction.