It's common practice in many organizations to effectively deploy new code with c... | Hacker News

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

		singron on June 4, 2019 \| parent \| context \| favorite \| on: An update on Sunday’s service disruption It's common practice in many organizations to effectively deploy new code with configuration changes. E.g. you write new code that is initially disabled then enable it with a configuration change. Since the code deploy didn't fail, you get a false confidence in the code and the configuration change seems like a safe "flag flip".

joshuamorton on June 4, 2019 [–]

I would phrase this a bit differently:

Binary version changes are a special case of configuration change that we (swes?) are particularly adept at managing reliably and safely.

But there are lots of other config changes that are potentially dangerous, and that we aren't as good at doing safely.

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