Expert Software Developers' Approach to Error
summary
Drawing on decades of empirical work, the main claim is explicit: experts treat error as opportunity and deploy concrete practices — tolerate defer compromise when triage needs it, and pair debugging and code review to surface assumptions. Examples include building deliberate faults to test harnesses, swapping tools to triangulate bugs, scripts that expose buffer overflows, and hardware-in-loop mismatches that reveal design gaps. Evidence comes from long-term observations across industry and concrete fixes and mitigations that actually find and patch real vulnerabilities.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:53active error
- 8:57deferring
- 14:10minding the gaps
- 16:00confirmation bias
- 16:54attending to contrary evidence
- 17:40understanding by breaking
- 26:13distinguishing between tools and goals
- 29:18reaching out
- 32:26contrasting multiple perspectives
related talks
49mExtreme Professionalism - Software Craftsmanship.
27m'The Art of Software Development'
32mTales of the Autistic Developer: The Expert
51mThe Art of Software Development
24mWhen expertise becomes our achilles heel
52mYour Brain on Software Development
19mA Career As Software Engineer
22mWhat Developers and Economists Can Learn from Each Other!
