Had a strange thought last year, that if a system runs too smoothly, eventually the knowledge of dealing with breakage will disappear, and when it inevitably breaks, everyone will be unprepared.<p>So a little bit of breakage is like a healthy "exercise."<p>Presumably, a functional system is supposed to have some kind of drills to fill in for that. But I have seen ones that don't!
Yeah, I've lived that one. When your system is falling over all the time, you get good at quickly bringing it back. When you have the first failure in 2 years and you didn't do drills or etc, it takes a lot longer to get things going again.
This is known as the "Paradox of Automation." It's a real problem for many industries.<p>The OG paper on this is called "The Ironies of Automation" (Bainbridge, 1983). It's a clunky but fascinating read. I give it a skim every couple years and usually come away with a bit of a fresh take on the problem.
Hence DiRT or whatever they call it these days
Very true. If things are too reliable, systems can come to depend on them always being so so reliable... So it can actually pay off to inject transient issues deliberately.<p><a href="https://netflix.github.io/chaosmonkey/" rel="nofollow">https://netflix.github.io/chaosmonkey/</a> and similar can help.<p>That said ... most instability is introduced with normal changes, so every engineer can be a chaos monkey. ;-)
Oh, the legendary backup restore drill? I'm sure it will happen <i>someday</i> ...
[dead]