How release canaries can save your bacon

Re:How release canaries can save your bacon by nurettin on Tuesday April 04, 2017 @01:16AM (#14029676)

You are a CTO sitting atop very expensive hardware and software. Would you start removing deployment and runtime safety guards (such as a consumer-facing staging environment) because you want to "discipline coders and devops"?

[ Parent | on HN ]

Re:How release canaries can save your bacon by d4mi3n on Tuesday April 04, 2017 @02:55AM (#14030153)

A post-mortem should never be about placing blame on individuals, it should be about identifying flaws in a system or a process.

There are places where post-mortems can turn into blame games, but in my experience such things are counter-productive to actually solving problems. Luckily, there are plenty of engineering organizations that do not make this mistake! :)

[ Parent | on HN ]

Re:How release canaries can save your bacon by qqg3 on Wednesday April 05, 2017 @07:14AM (#14041218)

The easiest way to avoid that is to have well structured post-mortem process, and post-mortem everything. Successful and unsuccessful releases.

[ Parent | on HN ]

Re:How release canaries can save your bacon by ojilles on Wednesday April 05, 2017 @08:59AM (#14041735)

We need to go from postmortem to postpartum!

[ Parent | on HN ]