Let’s be direct: Do you care about your users? Your business? Continuity, perhaps? Then long story short is yes, you need a reliability strategy. I know. It depends. It always does. But insight into reliability is valuable, especially when you can access it before things break. Perhaps the cracks are now showing in your service or some of the popular buzzwords are showing up in a roadmap nearby? Either way, it's a good time to talk about reliability strategies. Where I find this especially relevant: If you're working with: Containers and Kubernetes Internal developer platforms A team large enough to fight over merge conflicts CI/CD pipelines that break more than they build [if you're not able to ship your ideas from cradle to grave with ease, add more reasons] We are also here because in the early days (what do I even know :-p) functionality was a huge priority and while that remains relevant contextually, modern software environments are more complex and ...