Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Hot Take: Putting a deploy freeze in place does not mean you will be incident free.

I find this does not match my experience at all! The number one cause of incidents are code or configuration changes. Freeze those and the incidents DO go away 95%. Of course you need to update eventually and the problems will begin again, but freezing when there is the least amount of staff to fight fires is very sensible???

of course, nothing is 100% but let's not rock the boat so that the rare traffic based incident can be dealt with by the few staff that are there.



Anecdotally, configuration changes seem to cause the biggest outages these days.


We call them change freezes, they are generally done when there are less people around. This allows employees to celebrate holidays.

These do reduce, but don't elimate incidents.

Unilateral change blocks, stink, but don't put support in the weird position of taking on something they can't.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: