What Went Wrong?
The first step toward learning the lessons of the bug is determining what went wrong.
Haven’t We Just Done That?
Isn’t determining what went wrong exactly what diagnosis is all about? Yes it is, but what we’re talking about here is the bigger picture—how did the mistake make its way into the software in the first place?
For example, your diagnosis might be that the bug was caused by a failure to take into account the possibility of a network outage while receiving data from a server. That’s as far as you need to go during diagnosis. What we’re looking to do here is to work out why the original developer of the code didn’t realize that they had to handle network failure.
Get Debug It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
