Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
Been reading through the SRE book a while ago and consider this to be one of the "must-read" books these days. The Error Budget approach is pretty smart I guess. Challenge in practise: Your organization needs to have a somewhat working structure where a product owner, product manager, ... is explicitely made responsible not just for delivering new features but for overally earning money with features and components, which is development but also includes uptime and reliability of a service. Otherwise, (ensuring) availability will remain an Operations issue and the whole model will fail.
Been reading through the SRE book a while ago and consider this to be one of the "must-read" books these days. The Error Budget approach is pretty smart I guess. Challenge in practise: Your organization needs to have a somewhat working structure where a product owner, product manager, ... is explicitely made responsible not just for delivering new features but for overally earning money with features and components, which is development but also includes uptime and reliability of a service. Otherwise, (ensuring) availability will remain an Operations issue and the whole model will fail.
Agree, as per Second Law of Consulting by Gerald Weinberg:
Thanks a lot for reading!
Dan