Postmortem on the Ingen Incident
summary
A forensic review of Jurassic Park’s software and practices claims the engineered park fails: electric fences, visual scanners and power systems are brittle, undocumented and insufficiently tested, sabotage by a disgruntled contractor leads to four deaths, and frog DNA causes unexpected breeding despite all dinosaurs being female. Recommendations include chaos engineering (failure injection starting in dev), better budgets, transparency, hiring experienced engineers, incident-response training, and treating ethics as a resilience tool to prevent repeat catastrophic failure.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:27Review of Events
- 1:47Ethical Breaches
- 4:05Chaos Theory
- 7:26Application of Software
- 8:22Timelines and Scope Creep
- 11:10Malcolm was Right: Part One
- 11:43The Consequences
- 11:58Engineering Ethics and Chaos
- 13:09What is Chaos Engineering?
- 14:28Failure Injection
- 15:10Chaos and Ethics
- 16:06Appropriately Budget Resources to Software Design and Testing
- 16:48Use Chaos Engineering
related talks
10mThe Repeat Incident Fallacy: What Jurassic Park Can Teach Us...
47mBuild vs Buy: Software Systems at Jurassic Park
49mBuild vs Buy: Software Systems at Jurassic Park
28mWith great power comes great responsibility
31mPost-mortems: Building better software together.
20mPost Mortem Culture: Learning from Failure
37mChaos Engineering: The Fine Art of Breaking Stuff in Production on Purpose
40mBuilding Resilience: How to Learn More from Incidents