Maybe those who WFH during this situation will develop some empathy for full-time remote workers ... because for damn sure most of them have none. There are som

Maybe those who WFH during this situation will develop some empathy for full-time remote workers ... because for damn sure most of them have none. There are some issues that are obvious and easily addressed, like leaving stakeholders out of a meeting entirely ("couldn't find a room on short notice"). There are others that are hard to notice unless you're subject to them all the time. * A VPN that's OK for short-term use, but unreliable enough to cause multiple flow disruptions every single day. * Extremely slow (and often more contentious) document/code reviews because people aren't as comfortable with written communication as ftf. * Losing every commit race because of the above, and having to spend more time than anyone else handling tricky merges. * Being in effective listen-only mode in meetings because of constant interruption and side chatter (or not even able to hear if half the participants are loudly eating lunch the entire time). * IDEs that lose their ability to navigate code because the connection to the cross-referencing engine can't survive high latency. (BTW this is related to having a giant monorepo, which is itself a bit of a remote-hostile choice.) There are many more. Working from home has its advantages, but doing so in an office-first environment can be frustrating too. Maybe those who experience some of that frustration for a few days will at least stop criticizing others for things that aren't their fault.