Comment by Lutger
Totally. A lot of corps are ruled by management and sales people. Those often really enjoy talking and connecting, and it is a form of control for them. Of lot of these people think they can't do their job well if the quiet people (IT, devs) disappear into their homes. And they often genuinely think the workforce needs to have meetings and show up to be accountable. They don't really think about what IT people actually need, or they do sometimes but it won't be a decisive factor in the end.
I've worked in places where sales people were seated next to programmers, and the sales people were shouting through their phones continuously. The programmers complained endlessly about all the noise - without effect. First lockdown we had showed an increase of at least 300% productivity - hard and reliable numbers because all output was tracked voluntarily by the team (management never asked for this). Number of builds, commits, releases...everything was way up. It was quite shocking.
As soon as lockdowns were lifted managers began talking about being in the office fulltime, because it was so good to talk to each other and align your work. I remember working in a team that did 1 day a week at the office, that day we couldn't get anything done because everybody was just chit chatting all the time. Even if you wanted to - it was just impossible to focus.
Our security officer (CISO) remarked how the lockdown enabled him to think seriously about a security issue for the first time in almost two years. Isn't that tragic?
Companies are as rational as consumer behavior. You can't make this stuff up. Never attribute to malice that which is adequately explained by stupidity.
I'd be very interested to hear the perspective of your sales and management teams. Your view is obviously very biased and only tracks "productivity" from the programmers. "Number of builds, commits, releases" off-handedly does not sound like straight progress, typically fast direction changing (adapting to the business environment) from management and sales is what drives profit. Code is not an asset, it is a liability.
The loss of programmer productivity can easily be overshadowed by gains from other parts of the business. I know it's not always the case, and nobody wants to hear that their suffering is better for the company as a whole since it devalues your work, but I would be super curious to hear why the decision was made.