error handling patterns

AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment" — Real-world example demonstrating catastrophic failure

Describes a specific error handling pattern where user intervention is necessary to preserve context state.

[empirical_claim] "you don't get stuck anymore. Programming used to be punctuated by episodes of extreme frustration, when a tricky bug ground things to a halt. That doesn't happen anymore." — Article

Reviews primate incidents, adds guardrails" — Describes reactive safety pattern: infrastructure engineers review failures and add guardrails post-incident. This is a specific risk management strategy