I mean, that's a great example of a clear rationale! If my job required interacting with machinery or hardware that had to be centrally located, I wouldn't need

I mean, that's a great example of a clear rationale! If my job required interacting with machinery or hardware that had to be centrally located, I wouldn't need to be "required" to come into the office any more than I'm "required" to use Git to manage my code—I'm a professional, and that's just part of what I do. The issue comes up with roles when that isn't the case. In most programming roles I would not have any clear reason to be in-person, and even if I did have times where I clearly needed to be in the office, I would not appreciate being forced to come in outside those times. Requirements like that are frustrating because they require a real cost on my end (less flexible schedule, less control over my environment, a commute) and simultaneously signal a fundamental lack of flexibility, respect and trust from my employer.