diff options
Diffstat (limited to 'gemfeed/2021-10-22-defensive-devops.html')
| -rw-r--r-- | gemfeed/2021-10-22-defensive-devops.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.html b/gemfeed/2021-10-22-defensive-devops.html index b5ca5d09..f46becfd 100644 --- a/gemfeed/2021-10-22-defensive-devops.html +++ b/gemfeed/2021-10-22-defensive-devops.html @@ -45,7 +45,7 @@ </ul><br /> <span>That sounds a bit crazy, but this is, unfortunately, in rare occasions the reality. As the question is not whether production issues will happen, the question is WHEN they will happen. Every large provider, such as Google, Netflix, and so on, suffered significant outages before, and I firmly believe that their engineers know what they are doing. But you can prepare for the unexpected only to a certain degree.</span><br /> <br /> -<h2 style='display: inline' id='dont-fully-automate-from-the-beginning'>Don't fully automate from the beginning</h2><br /> +<h2 style='display: inline' id='don-t-fully-automate-from-the-beginning'>Don't fully automate from the beginning</h2><br /> <br /> <span>Do you have to solve problem X? The best solution would be to fully automate it away, correct? No, the best way is to fix problem X manually first. Does the problem appear on one server or on thousand servers? The scale does not matter here. The point is that you should fix the problem at least once manually, so you understand the problem and how to solve it before implementing automation around it.</span><br /> <br /> @@ -61,7 +61,7 @@ <br /> <span>Unfortunately, it will be a bit more complicated when you rely on code reviews (e.g. in a FIPS environment). Pair-programming could be the solution here.</span><br /> <br /> -<h3 style='display: inline' id='dont-make-it-worse'>Don't make it worse</h3><br /> +<h3 style='display: inline' id='don-t-make-it-worse'>Don't make it worse</h3><br /> <br /> <span>You want to triple-check that your script is not damaging your system even further. You might introduce a bug to the code, so there should always be a way to roll back any permanent change it causes. You have to program it in a defensive style:</span><br /> <br /> |