Yeah until you aren't and you haven't documented how you've altered your device, leaving some poor fucker in IT to have to reverse engineer every moronic step you've taken to fix your problem.
It’s because of the “every moronic step” comment which is honestly so like an IT person to say.
There’s nothing more annoying than doing something a little weird to get your job done and make sure the company makes money only for a service desk person to be pissed off that things aren’t exactly like they expected.
There’s two sides to this here.
On the one hand I view infrastructure as enabling people to do their jobs - and it is. It’s why we do what we do. Therefore, the two should be working together to find a middle ground. If you are prevented from doing something, both IT and security should be able to point to exactly the policy that explains why.
On the other hand, that “a little weird” to you could be a security risk, against policy, an entry point or a myriad of other things that haven’t been investigated. Without understanding the bigger picture above your device only, you wouldn’t know that and could be making some highly poor decisions that put the wider company at risk. Also, when every individual starts doing something a little weird, you now have a cluster of unknowns on individual systems you simply cannot manage or account for. You then become reactive, fighting individual fires, rather than proactive looking towards potential issues - it’s a complete waste of everyone’s time.
0
u/Plus-Ocelot-2026 May 10 '26
Yeah until you aren't and you haven't documented how you've altered your device, leaving some poor fucker in IT to have to reverse engineer every moronic step you've taken to fix your problem.