2 ms·
See.. my mind boggles that you think it has anything todo with personal trust. At a guess, you've been in that scenario, and it may well have been handled badl
by TristanBall 4y ago
See.. my mind boggles that you think it has anything todo with personal trust.
At a guess, you've been in that scenario, and it may well have been handled badly ( and i'll grant you it often is ), but you might also have taken it just a little bit personally?
It's not my current job, but I've been doing various forms of sysadmin for a long, long time.
Biggest security/outage risk in most companies I've work at?
Me. My teams.
Even after we've spent years and millions of dollars addressing those risks.
But it's not about trusting your devs, even if somehow, you think you can trust all of them, and all your future hires, every day, forever (!?!?!)
It's whether or not you trust all the software on their machine, everyday, forever. Which is just as ridiculous a statement.
Isolated dev environments aren't that hard to setup if you really need HW access.
Do it right and you might even end up with something better than local.
And no, I don't have admin on my current work laptop either.
Yes, it's occasionally annoying, and we have tighter controls than that, i cant do a bunch of things that most envs would allow without thought - and I occasionally set of alarms that trigger the security folks to have a word, which is also occasionally annoying.
Reassuring too tho.
And actually, slightly disappointed that's it's generally just a phonecall, and polite conversation, rather than black masked ninjas rappelling down from the ceiling yelling at me to step away from the keyboard, but you can't have everything I guess.