diff options
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi | 67 |
1 files changed, 59 insertions, 8 deletions
diff --git a/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi b/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi index ca098bec..ed0c2d66 100644 --- a/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi +++ b/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi @@ -3,7 +3,7 @@ How to stay sane in the world of DevOps ``` ) - ) (( ( + ) (( ( ( )) ) ) ) // ( _ ( __ ( ~->> @@ -23,19 +23,70 @@ How to stay sane in the world of DevOps ~~~~~' ``` -Log4shell (CVE-2021-44228) made it clear once again, that working in information technology is not an easy job (especially when you are a DevOps/SRE or security engineer or one of the team managers). I thought it would be interesting to summarize a few techniques to help you to relax. - -TODO: Mention CPU bugs here. +Log4shell (CVE-2021-44228) made it clear once again, that working in information technology is not an easy job (especially when you are a DevOps/SRE or security engineer or one of the team managers). I thought it would be interesting to summarize a few techniques to help you to relax. Also, not to mention the Meltdown and Spectre security CPU bugs we had to "patch" some years ago. => https://en.wikipedia.org/wiki/Log4Shell +=> https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability) +=> https://en.wikipedia.org/wiki/Spectre_(security_vulnerability) + +## Set clear expectations + +It's important to set clear expectations. It can be quite overwhelming trying to interpret and guess what others might expect or might not expect from you. If you know exactly what you are suppose to do, you can work towards a specific goal and don't worry about all the remaining stuff so much. + +However, if you are in a more senior position, it is expected from you to plan your tasks by yourself to a large degree. In this case, share your plans with your manager and/or the team and make sure that everyone agrees on it. Once done, be the execution machine. People will be happy to see that stuff gets done.Communicate clearly all critical work you do. This will also help to relax your coworkers and managers as they see that progress is made. + +Due to politeness, many people are afraid to set clear expectations. I personally may sound a little bit "too german" when setting expectations, but so far nobody complained and I have only received positive feedback. So maybe it's just me who thinks that I am "too german" for the english (as of writing this, I work in England, London). + +## Always respond to requests but set boundaries + +There are many temptations to get side-tracked by other projects and/or issues. It is important to set boundaries here. However, always answer to all requests as nothing is more frustrating than asking a person and never to get any answer back. This is especially frustrating when everyone is working form home and people are using tools such as Slack and E-Mail for 90% of their communications. Here, set clear expectations again. + +If the request is urgent and you have the capacity, help. If it's not urgent, maybe ask to create a ticket. If it is urgent but you don't have the knowledge or the capacity to help, try to deffer the request to one of your teammates. You could also pride some quick tips and hints, so that the requester can resolve the issue by himself. Depending on the urgency, you may also ask the person to come back a few hours later. Also, make it transparent to the requester why you might not have the time now as this can help the person to review his own priorities or to escalate. + +Sidenote on escalation: Never make it personally. The only forms of escalation should be due to technical issues or lack of work resources. An escalation then becomes like a math equation and does not need human resources involved. So per-se, an escalation is nothing negative but just a process people can follow to help decision making. + +## Go slower even though you could go faster + +When working in a team, you may feel that you could get done things faster when you just did everything by yourself. This can be a bit frustrating at times, as you might need to work late hours and also might need to explain things over and over again to others. + +Security is a team effort. 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 (e.g. Software Engineer) knows how to use all the tools so well like a full-time DevOps or SRE person. As a DevOps/SRE person, you are not a security expert, though. Security experts are different people in your company but you (DevOps/SRE) 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? + +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 a scripting language), 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 lacks the domain knowledge of the software you are patching): + +=> ./2021-10-22-defensive-devops.gmi See also: Defensive DevOps + +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 super hero. + +## You are not a super hero + +Always keep that in mind. You can't solve all problems by your own. Maybe you could, but that would be a lot of additional pressure and stress. Also, Superman and Wonder Woman would receive probably a much higher salaries than you ;-). + +I have been a super hero multiple times mitigating critical incidents (they were not security related though) and I was proud about it. But actually, I should not have been proud of it, as for everything there should be other people around who should be able to resolve an incident. No company should rely on a single person, there must always be a substitute. You are not a super hero and as harsh as it sounds, everyone is replaceable. Every super hero can be replaced with another super hero. The only thing it takes is time to get to know the infrastructure and tools very well paired with work dedication. + +This doesn't mean, that you should not try your best. But you don't need to try to be the super hero. Maybe someone else will be the super hero, but that might be OK as long as it's not always the same person. Everyone can have a good day after all. + +If you are a super hero, try to give away some of your super powers, so that you can relax in the evening knowing that others (e.g. the on-call engineer of your team) knows how to tackle things. Every member of the team needs to do DevOps (even the team managers and of course also the Software Engineers). Some may be less experienced than others or have other expertises, but to counteract this you could document the recurring tasks so that they are easy to folow (which then later could be either fully fixed or automated away). + +So you are not a super hero. Or, if you are a super hero, then all colleagues are super heroes too. + +## Force breaks; + + +## Shutdown routine + + +## Time for personal advance -# Set clear expectations +Time blocking -It's important to set clear expectations. It can be quite overwhelming trying to interpret and guess what others might expect or might not expect from you. I am even receiving positive feedback when setting boundaries at work. +## Think positively -# Go slower even though you could go faster. +If times are very stressful, think that it could be worse: -# Shutdown routine +* Nobody is dying, we are only doing some IT security stuff. +* Your time after work is your own time, look forward to time with your family or a nice dinner. +* Your IT job and life is actually pretty good (e.g. compared to an homeless person or a cleaner). +* You probably never will run out of work in the IT sector. So you will always be able to make a living. # Book recommendations |