As a developer, WFH actually facilitates things like pair programming and peer review. Especially for introverts like myself, it is much easier to do a screenshare of your IDE and review code in a group than try to sit next to each other or review code on a big screen in a meeting room. This has become a thing for us now (let's jump on a zoom and i'll show you quickly), for anything that's too complex to slack.

The ability to easily screen share and record sessions as needed means I can get the big picture in the initial live session and review the details later via recording as needed (especially those nitpicky code details nobody remembers the first time around).

I will miss this when we have to go back to the office.

Bad latency, pixelated screensharing, frequent issues with sound and video. On top of that hardware problems with bad microphone setups, cross talk, etc.

I hope that at some point someone is going to show up and take this seriously. Treat it like a medical service, or a least close to. But I'm not holding my breath. I believe it was least year that I read that John Carmack had measured the latency of his cell phone and found it to in the vicinity of 700 ms.

For all we know, their password might be something like "remote_worker"!