Debugging Like House - Software Differential Diagnosis
summary
Apply House-style differential diagnosis to stubborn bugs: list every symptom on a whiteboard, enumerate possible causes, then design tests to rule in or rule out causes and pick the single most informative test rather than the obvious first one. Use a real or virtual whiteboard or even a rubber duck to iterate. Claim: this method resolves many elusive issues that otherwise take days or weeks; observed usefulness on ~90% of routine problems and on the rare multi-day mystery.
AI-written summary · about
related talks
27mDebugging product engineering organizations
37mThe Bright Future of Debuggers: Challenges and Opportunities
14mShow Me Why It's Correct: Saving 1/3 of Debugging Time in Program Repair with(…)
29mKeynote: BDD - Bias driven development
21mAbstract Debuggers: Exploring Program Behaviors Using Static Analysis Results
44mBehavioral Software Engineering
50mTest Intelligence for Architects
42mWhat our Brains can Teach us About Software Engineering