3 ms·
There's an important lesson there for all of us: the guy screwed up majorly, but the systems in place let him. If our own systems don't protect our company from
by kstrauser 7y ago
There's an important lesson there for all of us: the guy screwed up majorly, but the systems in place let him. If our own systems don't protect our company from a drunk senior dev at 2AM pushing code to the master branch and deploying it, then we're really no better than his employer was.
I used to dislike how restrictive some policies can feel. Now I can appreciate that at least some of those policies protect me by making it hard for me to exercise poor decision making without my coworkers signing off on it.
(Note: "some". "Security theater" is still very much a thing, but turns out that not all pain-in-the-neck controls are there just to be annoying.)
- nonbirithm 7y agoI once brought this up to someone because the databases we used for testing were sitting in our organization's resource group to be modified globally, and I wanted to ensure there was a backup in case we messed up something, or at least restrict access to our team. The data went back years and there was no clear way if reproducing it if something went wrong. He said no, and didn't allow me to, on the basis that you're being trusted to work here, so you're also being trusted not to mess with anything you don't need to. Therefore we didn't have to limit access to anyone. I felt that was missing the point since there could also be accidents.
- downerending 7y agoEarly in my career, I wanted "root" on every system I could possibly have it on, and often bristled if I didn't get it. Late in my career, when someone asks me if I want "root", I often decline. There's a lot to be said for limiting one's exposure to those risks and having solid plausible deniability if someone hoses some crucial system. (Not to mention being "unable" to access a lot of systems at 3am to help fix messes someone else made.)
- kstrauser 7y agoAbsolutely! I found out I still had access to my account for a previous employer on some random industry website when my 1Password autofilled the login and it worked. I contacted my old boss and asked him to immediately remove my access, and confirmed that I couldn't get in anymore. The last thing I want is for something to change or break, and for them to say "hey, that's funny, our old employee is still logging in..." I actively don't want to have access on things I don't need.