3 ms·

I want to minimise the number of times that a single person "being careful" is the difference between a smooth experience and an extended service outage. I als

I want to minimise the number of times that a single person "being careful" is the difference between a smooth experience and an extended service outage. I also favour responding to mistakes quickly over preventing them completely. I've seen a lot of teams where there was the one keeper of the systems who knew how to do all the deployments and migrations. In every situation they became a bottleneck for the team, and prevented any real improvements being made.

folkhack 7y ago
In my experience you literally can't idiot-proof ops. In every operational role I've ever been in there's still very trusted people hammering out commands with very privileged accounts. Even at my last role people would get angry at me when I'd ask for "command confirmation" and/or "an extra sets of eyes". In my world, I favor getting it right vs. responding to mistakes. It's the difference between "scalable" and "firefighting". Having a SPF asset who holds the keys to the entire kingdom is a completely different problem, and a different conversation.