The Science of Engineering Incidents and Identity: Why It's Rarely the Villain's Fault

TEST_YOURSELF · How well do you know this science?

1. 01 What does James Reason's Swiss cheese model say about how complex systems fail?

   One careless person is always the root cause of any serious failureFailures happen when holes in multiple defensive layers align simultaneouslySoftware systems fail due to insufficient testing by QA engineersComplex failures are random and unpredictable by nature

   Reason's model shows complex system failures are multi-causal: a series of holes in otherwise-robust defensive layers must line up for an accident to penetrate to the outcome. No single person creates all the holes. source ↗

2. 02 According to Google's SRE Book chapter on postmortem culture, what is the primary purpose of a blameless postmortem?

   To identify and formally reprimand the engineer who caused the outageTo document the incident, understand all contributing root causes, and put preventive actions in placeTo create a public record of what went wrong for customersTo justify reducing the team's on-call rotation size

   Google's SRE Book states that the primary goals of a postmortem are to ensure the incident is documented, all contributing root causes are understood, and effective preventive actions are put in place — not to assign fault to individuals. source ↗

3. 03 What did Champion et al.'s 2024 study find about infrastructure and glue work in open source software ecosystems?

   Infrastructure engineers are recognized more often than feature engineers due to incident visibilityGlue work like documentation and code review is systematically under-recognized compared to feature commitsOpen source maintainers are well-compensated for invisible work through community grantsThe study found no significant difference in recognition between different types of contributions

   Champion et al. found that infrastructure maintenance, documentation, code review, and community management are structurally invisible in most recognition systems — despite being essential to the ecosystem's functioning — while feature commits attract disproportionate credit. source ↗

4. 04 According to the 2025 Stack Overflow Developer Survey, what is happening to developer trust in AI-generated code?

   Trust in AI-generated code is at an all-time high as models improveTrust in AI output is at an all-time low among developersDeveloper trust in AI is unchanged from prior years — concerns are overblownDevelopers trust AI for documentation but not for code generation specifically

   The 2025 Stack Overflow Developer Survey found developer trust in AI output at an all-time low — the majority of developers do not fully trust AI-generated code, despite the rapid proliferation of AI coding tools. source ↗

5. 05 What did Allspaw and Robbins find about the effect of blame culture on engineering incident investigations?

   Blame motivates engineers to be more careful and reduces future incidentsFear of punishment causes engineers to withhold information, which degrades reliability over timeBlame culture has no measurable effect on information sharing in postmortemsBlame should be applied selectively — only to engineers who violated written procedures

   Allspaw and Robbins documented that fear of punishment causes engineers to hide information about what happened during an incident. That hidden information prevents the organization from understanding and fixing the real conditions — making the next incident more likely. source ↗