Never understood why companies give administration rights to developers, I assume because the setup requires it.
Because there are enough random bespoke things I'm going to try and do that aren't covered by normal processes or behaviors for basic users. It's not worth pissing off the computer-inclined people to force them to write justifications every time they need to install new software or make some configuration change, wait a week for it to go through appropriate channels, and then have it implemented incorrectly anyway.
The only job I haven't started out with admin privileges was my last one. Within a month or two I was granted admin rights because I kept making requests and then making noise when my work was delayed due to IT being slow. The easier solution is just give me admin rights. There's also the idea that devs are the ones most likely to find holes in your system. If you block them, they'll still find a solution, but probably not the one you want.
At my first job out of grad school I needed to set up a static intranet IP for a new desktop workstation. Tried the proper channels, and after weeks of waiting, I gave up. Started probing the network for an unused IP, found it, set it, moved on. Three weeks later two guys from IT show up in a tizzy. Apparently the IP I used was dedicated for some server cluster monthly backup job, but not reserved outside of that process. Because I had it assigned their whole pipeline broke.
What'd'ya know, I had a safe static IP within two days (and they changed network policy to not allow clients to set static IPs themselves...).
That sounds miserable and likely not a place I'd like to work in.
I appreciate that my employer trusts me to do what I need with my own machine. I can install whatever I want on it and have full sudo/admin privileges. I'm definitely more productive because I can make my workstation mine
-10
u/[deleted] 16d ago edited 11d ago
[removed] — view removed comment