Lots of good discussion here - finally caught up. To touch on some terms used in this thread, my wife and I are both educated "knowledge workers" each with a "hybrid schedule", and we are grateful for the "privilege" that affords us. We've adapted, but don't take anything for granted. We bought a house within reasonable commute distances for each of us, even though neither of us see 100% office work on the horizon. But you never know.
She is in mental healthcare, which is probably the best application of telehealth. It is much more flexible for both patient and doctor, and has given access to many patients who otherwise live too far away from services. Some clients are better served virtually, due to their specific anxieties and disorders etc. But some clients are better served in person, especially small children with small attention spans, so she still goes to the office two days a week. She is not mandated to do so, but it is heavily suggested by her boss that she keep two days a week of in-person clients to continue serving a broader spectrum of people and keep both sets of skills sharp.
I design stuff in CAD, analyze and validate designs, specify and procure components, and mostly manage my own work. I do a ton of this from home, and it's great. Keeps the miles off my cars, more time in the garage, etc. But I also build stuff and run tests in the lab. I can't do that from home. I work with machinists and technicians who also build my stuff, and they sure as hell can't WFH. If I want my stuff built right, it's best for me to be there, talking face-to-face. Most of my meetings with other engineers or project managers are virtual, even when I'm in the office, and even when we're all in the office (LOL). It's just easier to screen-share than to set up all the conference room multimedia crap. My workplace does not mandate coming to the office, but in order to keep a physical office space, we have to come in 60% of the time, otherwise you considered fully remote and have to use the flex space. In practice, I typically WFH 2 days a week. Sometimes more if I'm deep into design, sometimes less if we're slapping parts together.
The other piece of it is learning from others in person. I can poke my head into another engineer's office and quickly ask about a best practice for a specific problem. I do this on chat too, but I find more learning happens with in-person discussions, because they tend to meander and go off-topic, we break out the whiteboard drawings, start talking about LS-swaps, and I learn about old projects and problems and how they were solved. More time wasted talking, sure, but also more institutional knowledge is built, so is a relationship. On a web chat, I get the answer I wanted and nothing else, if I even bother asking. But I'm pretty far into my career, so this is way more important for junior engineers.
I'm not pro-WFH or anti-WFH, there is always nuance. I agree with the sentiment that WFH is not for everyone, it's not for every business, or every line of work, but those employers and individuals who can find the correct balance for their specific set of needs will succeed. Adapt or die - that's the story of evolution and human history.
Like most hot-button issues, on a scale of 1 to 10 the vast majority of us lie somewhere between 4 and 6, yet we pretend like everyone is a 1 or a 10.