Normal Errors: Anatomy of a Collective Giving Up
summary
Examines why software teams learn to ignore recurring exceptions in logs instead of fixing them, naming the problem as a collective psychological shift from urgent anomaly to accepted background noise. Uses classification of these recurring "domestic" errors and discusses practical responses—ranging from fixing to filtering logs—to understand when and why teams choose not to act.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:44Normal errors defined
- 1:45Costly app case study
- 3:12Developer pets metaphor
- 7:08Denial curve and giving up
- 10:59Social impact and broken windows
- 12:51Legacy risks and tech debt
- 13:32AI and verbose logs
- 13:543 Rs against normal errors
related talks
36mThe Exceptions We Don't Catch in Technical Conversations
34mWhy Good Software Goes Bad
52mUnderstanding UnHealthy Syndromes of Software Delivery
49mBugs in Collaboration: "Learning from Incidents" Edition
05mMental models
38mFallacies of Software Development
44mBehavioral Software Engineering
01h 00mCognitive biases in software development