++ categories = [“method”, “devops”] date = “2015-01-21T19:20:10+02:00” description = “Ownership, expertise, and the right to fail” draft = true keywords = [“fail”, “failure”] title = “Let them fail”

+++

During the SRECON17 Eu, part of the bird of features Building SRE in small orgs, I explained what I would sum-up as “Ownership is a right for failure”. As I also had the same discussion in different contexts, let’s try to write something there.

// # Fail! // https://projecteve.com/wp-content/uploads/2014/03/small__6167125536-233x300.jpg // // One of the stupidest sideeffect of the “Fail fast, fail early, fail often” methodology,

Context

Why? time to discuss experience instead of too much theory

Breaking bad

In this post, what I call a break is an outage of a resource. It could be a silent one, like a failing instance. It could a hard one with an impact on the users. Avoiding them is part of the existence criteria of a company and we work hard to avoid them but they come.

If a fact is coming back

the Use of breaking

Having a break

Breaking is not failing Don break too much

#https://www.azlyrics.com/lyrics/linkinpark/nobodyslistening.html

I hate my rhymes, but hate everyone else’s more