…ncluded being open to deploying bad releases which could break functionality and hurt the business. This was due to the assumption that releasing code more often is riskier. It is, in fact, the opposite since shipping less often means shipping more changes at once and the more changes there are, the riskier it is. The extreme opposite of this is that if a deploy breaks functionality and we only shipped a one-lin…
I speak to plenty of engineers who are both 1) correct that the root cause was product (or sales, or _____), and 2) fail to see that they (and their leadership) are part of the problem now, if not the problem. They’re expecting a massive mea culpa (we are to blame, and we’re sorry) from the rest of the orga…