Earlier quoted context omitted.
Speaking from experience, the “culture” at Microsoft and Google (at least) definitely varies more between teams and divisions than between those two companies on-the-whole.
Fair enough. Nadella's hard push for the return is curious to me (I'm in the Seattle area, and close-ish to the campus with quite a few friends who work in a single team, so I'm a bit myopic, I suppose). They all seem to do well remotely, and I do also. I probably do work less hours, on the whole, but I produce more... so I dunno how that factors in. I can't speak to their quality of work, though.
In the short term, it would be better for the more experienced developers to be more productive, because their time was worth more, but eventually the experienced developers will leave. If new people aren't trained to replace them fast enough, the system becomes unsustainable.
There are several other areas where eliminating certain activities provides short-term productivity gains at the expense of long-term cohesion. All hands meetings about company direction can be delayed for a month with no negative impact, but if I skip all large company meetings for a year I'd have a much harder time prioritizing tasks (it's unclear which contribute directly to the company's long-term plans and which are busy work) and no idea how to route serious issue only tangentially related to my team.
It's entirely possible there's a looming but currently well-hidden pipeline issue companies are anticipating and trying to avoid.