Hey blog, long time no see. I’ve been incredibly busy these last couple months. Apologies to you for not updating your content as often as I’d like to. I intend to post this in HackerNews, so if you’re coming from there, hello 👋 ! Recently, someone approached to me in Reddit asking me if I had any general advice for an “first time | entry-level | junior DevOps Engineer” While I disagree on that request because I believe that: ...
It has been a while since I’ve been working as SRE/Platform/Cloud Engineer, and lately and I realize I’ve been repeating some questions to developers that I rarely get an answer for straight away. These are not meant to make anyone’s life harder, au contraire, the whole pourpose of having a solid answer to this list of questions, is to make everyone less worried about the probabilty of some high stakes, overnight failure or a data handling missuse that could potentially cause big losses, and of course a lot of unnecessary stress. ...
I just found this precious little jewel on the internet. The HumanOps-mantra I’m re-posting here as I strongly believe in every single point made in it. HumanOps Mantra Humans build and fix systems. Humans get tired and stressed, they feel happy and sad. Systems don’t have feelings yet. They only have SLAs. Humans need to switch off and on again. The wellbeing of human operators impacts the reliability of systems. Alert Fatigue == Human Fatigue Automate as much as possible, escalate to a human as a last resort. Document everything. Train everyone. Save time. Kill the shame game. Human issues are system issues. Human health impacts business health. Humans > systems