The problem areas — and the reason you’ve basically all got to be in the office at some point — are decision making ones where a group of two or more people fervently believe in two or more mutually exclusive ways forward. Even when I worked remote for a company multiple timezones away, I would be in the office one week every quarter to first build social capital and later to cash it in when building consensus.
I also think back to one of my stakeholders was an underperforming SWE intern. The rate of online engagement that best suited them was zero, and yet — as with any intern — it was crucial to us that they left feeling positive about their time here. That stuff is really hard over the phone.
And you force everyone to commute into the office.
I've been working remotely for 6y; we have multiple external business partners, and a team of over 50. We have team members and business partners in Russia, Finland, Sweden, Germany, UK, France, NYC, BC, Cali, Japan, and elsewhere; we operate without core hours. I, personally, regularly interact with people in all those listed locations every day.
Never once has there ever been a need for an in-person meeting. Never.
Those kinds of situations are much easier to keep on track in a call / video conference, and easiest in person, when you can have ad hoc conversations after the meeting has ended. (Video conference products I have used — all the standard ones — don’t really have a way of ending a meeting other than hard-stop-return-to-isolation for all participants, whereas in real life it’s much smoother and more continuous than that.)
Not all tech work is about sitting in front of a glowing screen, writing code. It’s about achieving a business goal that brings in revenue, and all the alignment throughout the org that’s needed to get that done.
Repository layout, test framework changes, factoring out core components to make a long term stable branch, persuading teams to collaborate at their bleeding edges rather than by internal releases, how to ship auto formatting code with the lowest negative impact on everyone else…
Decision making, even on technical topics, is a people-centric skill.