diff options
| author | Paul Buetow <paul@buetow.org> | 2021-12-26 16:09:37 +0000 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2021-12-26 16:09:37 +0000 |
| commit | bb8ea164a610d97592d80e3cfee879974e5d06b6 (patch) | |
| tree | db45a401b58c3888cb71da3996b694fcee4166ac /gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html | |
| parent | 080b45fcd07a531754ca4045a40c94675c38ad40 (diff) | |
new style
Diffstat (limited to 'gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html')
| -rw-r--r-- | gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html index 7516f9fd..799674a4 100644 --- a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html +++ b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html @@ -56,7 +56,7 @@ <p>Security is a team sport. So slow down and make sure that everyone is on track with the goals. You can go full-speed with your very own subtasks, though. Not everyone knows how to use all the tools so well like a full-time DevOps person. As a DevOps person, you are not a security expert, though. Security experts are different people in your company, but DevOps will be the main tribe deploying mitigations (following the security recommendations) and management will be the main tribe coordinating all the efforts. So even if you think that you can do everything faster by your own, can you really?</p> <p>(PS: When I mean DevOps, I also mean Site Reliability Engineers and Sysadmins. I believe SRE and DevOps are just new words for Sysadmins, in most cases).</p> <h3>Don't rush to prevent errors</h3> -<p>Slowing down also helps to avoid errors. Don't rush it, even if the task you are working on is urgent. Try to be quick, but don't rush it. Maybe you are writing a script to mitigate a production issue. You could others peer review that script, for example. Their primary programming language may not be the same (e.g. Java vs Ruby), but they would understand the logic (Or let another DevOps person from your company with good scripting skills review your mitigation, but he then may lack the domain knowledge of the software you are patching.</p> +<p>Slowing down also helps to avoid errors. Don't rush it, even if the task you are working on is urgent. Try to be quick, but don't rush it. Maybe you are writing a script to mitigate a production issue. You could others peer review that script, for example. Their primary programming language may not be the same (e.g. Java vs Ruby), but they would understand the logic. Or ask another DevOps person from your company with good scripting skills review your mitigation, but he then may lack the domain knowledge of the software you are patching.</p> <a class="textlink" href="./2021-10-22-defensive-devops.html">Read also "Defensive DevOps" about deploying mitigation scripts.</a><br /> <p>So relax, don't always expect immediate results right away. Set clear and reasonable expectations to the management about the mitigations. You are not a superhero who has to do everything by yourself. Sometimes, you will miss a deadline. But that will have a good reason. Don't rush to complete just to meet a deadline. </p> <h2>You are not a superhero</h2> |