The article discusses the evolution of incident response and analysis in the software engineering industry. It describes the current industry standard for incident response and the importance of incident analysis in improving software reliability.
The article also warns against the dangers of incident legalism and advocates for a holistic approach to driving reliability, using systems modeling as a helpful tool.
The author provides three simple rules for investing in reliability: invest in response, analysis, and remediation; allocate most of the energy towards remediation; and consider alternative solutions before increasing investment.
















