I just gave you an actual, practical example, not a theoretical one.

Here's another one. I wanted to try eca-emacs, the documentation website sits at https://eca.dev, Cisco Umbrella, for whatever stupid reason, blocks the entire .dev domain, and every corporate laptop comes pre-installed with Cisco Secure Client that you can't remove. I submitted a ticket, and then wasted my time on a ridiculous exchange with the "big security guy," who decided to take a power trip and refused to have the website whitelisted. Despite it being absolutely harmless. I don't know where the fuck he's purchased that condescending tone and posture. In the end, I said: "thank you for your time," and hoped to never ever have to talk to him. Then I set up a SOCKS tunnel through my local Linux box, installed the FoxyProxy extension, and voila - I'm never ever going to have to complain about a blocked website.

> sysadmins had the final say

And you can always find workarounds. Those who want to do something look for a way, not excuses. You're a goddamn computer programmer. Maybe act like one.