9 ms·
I’m curious what the reprocusions are, if any, once a post mortem is completed and teams or individuals that contributed to the outage are identified. Is “causi
by dawhizkid 8y ago
I’m curious what the reprocusions are, if any, once a post mortem is completed and teams or individuals that contributed to the outage are identified. Is “causing” this a fireable offense?
- beckler 8y agolol, like employers need a real reason to fire someone in this day and age
- NathanCH 8y agoIt shouldn't be unless there was malicious intent.
- selectiveshift 8y agoNot unless there was malicious intent or willful negligence. Amazon is a data driven company. The data shows that a “blame” culture results in more incidents. (Airline industry taught us this: https://www.faa.gov/about/initiatives/maintenance_hf/library/documents/media/human_factors_maintenance/understanding_the_safety_culture.a_communicational_approach_to_%60blame%60_options_in_asrs_incident_report_narratives.pdf https://www.faa.gov/about/initiatives/maintenance_hf/library...)
- smt88 8y agoDo you know this from experience? Or are you just guessing?
- smt88 8y agoMy friend was fired years ago for an AWS outage that took down Netflix. I don't know any other details, but should ask him.
- dlgeek 8y agoNo. Amazon's culture is super big on blaming the system. I know of incidents where operators made mistakes doing stuff that directly caused really big outages - the postmortems were entirely about the (lack of) safety of the tooling involved that allowed a single person to make such a mistake, and involved examining all the tooling of entire business units to try to identify other tools that could have such an impact. No individual blaming is involved - and in fact, postmortems always refer to "the engineer" or "the operator" and never include names.