Not exactly the most productive WFH conditions.
Most Junior engineers aren't working remotely. I've been working remotely for a decade with different companies and almost all of the developers on my teams have been mid-level to senior. The junior developers always struggled and had so many roadblocks, it made working remotely difficult.
It's really not that difficult to replace an in-person meeting with Webex voice call and/or screensharing. I go onsite once every 3 months for a couple of hours and it's all that's needed.
Our meetings regularly have 10+ people from different departments.
This is very much not my experience. I don't know what field you're in or the structure of your company, so I don't want to hazard a guess as to the difference. But the majority of the time I call a meeting, it's to have a fairly complex, dynamic conversation for which the communication bandwidth of Slack/email/GDoc is too low (otherwise we'd stick with async/chat). This means that few meetings consist of conversations that're fairly predictable. Which means the person running the meeting needs to know when to cut a conversation off or let it continue, what direction to take the conversation, pick up on silent hesitancy or disagreement from any of the ten people in the room, etc etc etc. I can go on and on about the techniques I've seen people use to run extremely effective meetings, as well as how poorly-run meetings don't use them. As mentioned, these rely on visual and timing cues that humans use to communicate, sometimes unconsciously. (I'm keenly aware of good and bad meetings because I hate meetings)
Only for people who can't read.
If you seriously think written text is as communicative as face to face communication, I would consider being evaluated by a professional for a social interaction disorder of some sort.
Of course, you could learn to write better and convey the same information over text.
Of course there’s still noise. Just like in text. Professional writers struggle just as hard to get their word choice and phrasing -just so-.
I'm looking forward to AR/VR taking over more cake of the need for physical needs.
Non-verbal communication is a huge part of social (and this includes work) interactions.
https://en.m.wikipedia.org/wiki/Bandwidth_(computing)
Here's some information on terms you're clearly unfamiliar with that I used in the part you quoted. In the future I suggest you try and understand the words you're reading _before_ making a fool of yourself, but you do you. Hope that helps!
Basically, I think the key is latency. If you need to communicate two-way to work out issues, then you want low latency (because each response of yours depends on the other party's last response), so speech is quickest. (There's also texting, but that sucks because the data entry method is so slow; I don't know why so many people prefer it to talking, even for conducting intimate relationships.) However, if the communication is one-way (like your company disseminating some general information for all employees), then at least for me, reading is much, much faster than listening to someone talk.
I find almost all meetings to be a waste of time. Maybe 1:1s are the exception, but they're also pretty much optional - good to have a catch up with team members sometimes but if someone can't make it that day no big deal.
The problem with meetings is that a well run meeting needs to have an agenda and ideally written minutes, I don't think anyone disputes that (except for casual 1:1 catch-ups which don't). So you end up writing anyway, or wish someone had. Without the writing aspect meetings are often poorly disciplined, achieve little, run over and end with an agreement to organise another meeting.
In the end, work - the production of useful artifacts customers will buy - gets done alone. It doesn't get done in meetings with colleagues.
I was a wfh maximalist like many on this thread at the very beginning of my career, but AFAICT it just comes from some combination of a) being a junior engineer that works on isolated bits of work and didn't need to communicate cross-team much or b) having work that doesn't require much creative collaboration. As I got more senior and moved towards different types of problems, my appreciation for the value of (though I still do enjoy and make time for WFH).
For those who say that Slack or email or VC are perfect substitutes: there's no substitute for the high-bandwidth, low-latency medium of personal communication. Get good enough at running meetijgs of more than two people and you realize how much of the task of efficiently running a meeting involves reading micro-expressions and pauses to pick up on cues that help you direct the conversation (not to mention having n points of failure in a VC being accessed by n network connections). My team has been remote for a week and I've already noticed good meeting runners have worse meetings and bad meetings runners have even worse meetings.