Earlier quoted context omitted.
You seem to have missed my point that all of those options require someone to actually be at their workstation and available. With WFH, half the time people aren't. In the office they are. If WFH is going to be the future, then there should be uptime requirements with associated penalties so that someone is as available as they would be in the office. Software development is a team sport, you don't get to walk off th…
> require someone to actually be at their workstation and available. No guarantee people will be at their office desk either to be frank. They could be hiding in the toilet, loitering at the water cooler, out on smoke break, getting coffee, ... etc.
Which goes back to the principle that WFH is more beneficial for senior devs than juniors. If you lack the knowledge or authority to work independently for extended periods, then instead of everyone being on the same objective schedule the junior people are forced onto whenever the senior people want to work, and more specifically when they want to be available to answer questions that only they can answer. It's like only being able to do homework during a professor's office hours.