You know, one thing that I don't see discussed much is: Just like more advanced programmers worry about the worst case scenario of some code you've written rat

You know, one thing that I don't see discussed much is: Just like more advanced programmers worry about the worst case scenario of some code you've written rather than just the average -- with these remote working policies, sometimes the question is not just, will it make everyone on average a more productive employee, but what is the worst case that might affect your team under very tolerant remote work policies? Because if a few people's decrease in productivity is so noticeable working remotely that the team in general suffers / no longer works well, then it's a different consideration. There is something difficult to quantify about the notion that when a few people on a team start being less responsive /interactive, it can have a real impact to how people think of the pace of what you want the team to operate at. Especially if you're doing prototyping / early stage creative work where you're not operating by tickets, but rather looking over each others' shoulders to give live feedback and trade ideas. Not everything about work is to be designed to simply give what the employees would naturally want.