Suggestions
Tim Lewis
I.T. at Oversight Systems
Tim Lewis is a seasoned IT professional with expertise in IT analysis, software development, testing, and cloud consulting. He is proficient in UNIX, Linux, ETL, ELT, Salesforce, Elixir, Phoenix, Erlang/OTP, Oracle, SQL, C, PKI, Git, and Proxmox. Tim holds a B.Sc (Hons) degree in Computer Science from Coventry University.
Tim Lewis has a rich professional background having worked at various organizations. He served as an IT professional at Oversight Systems and also worked as an IT Consultant at CloudTau, Verizon Wireless, and ALLTEL Information Services.
Highlights
An insightful analysis of the Crowdstrike incident (17m watch), highlighting the mechanics of OS kernel mode code, and the importance of rigorous testing and validation of function inputs in order to reduce the chances of such fiascos. The piece also touches on crisis management strategies, identifying James Burke's exemplary leadership at J&J. Crowdstrike ought to have known how to engineer that kernel mode code properly, and can glean valuable lessons from Burke's approach. Companies that are exposed to being the source of such problems would do well to learn those lessons before the day they need to put those plans into action. Watch the analysis here: https://lnkd.in/gfx6F4m5. For more on James Burke's crisis management legacy, check out: https://lnkd.in/gjWnkrkx #crowdstrike #crisis #crisismanagement #kernel #ring0
If you are not creating devops runbooks as part of every software project then you are setting yourself up for repeated errors, escalations all the way back to developers, and higher ongoing operational expenses and disruption of other projects. The responsibility for this is with management, who all too often fail to include creation of runbooks as a mandatory part of the project lifecycle. You must improve those runbooks on an ongoing basis. This article explains how, by implementing feedback loops between ops and devs. It also touches on the importance of sharing knowledge, and why having "rockstars" in your company is often a red-flag that can signal the presence of toxic and expensive practices, rather than being a good thing. Having good runbooks also helps with hiring and training. No fancy tools are needed to get started: an in-house Wiki works. In short, make sure you are documenting your procedures as you go, don't let devs cop-out of improving those procedures, and share what you know in order to help those around you improve their game. Be a sharer, not a hoarder. https://lnkd.in/dVJ83Kj
