Methodology of Bug Fixing
Subscribe to the 
RSS Feed or by Email and receive free daily updates
In this very well written article on How to fix a bug, Tim Hastings lays out a detailed step by step procedure to successfully squash the bugs.
Beginning with a definition of bug, he goes on to classify bugs as Logical Bugs and System Bugs. He then elaborate on 3 steps required to fix a bug:
- Recreate the problem: Hunt for clues, visit the crime scene, wait for acts of randomness, mirror like live
- Prioritize the Bugs: Class A, class B, class C
- Locate the bug: Tracking it down, assert your assumptions
- Fix the bug: how to fix a logical and a system bug, beware of side-effects, testing the fix, version control for source code.
He further mentions that the more experienced you are fixing bugs the better you get at it. I totally agree with you Tim, but I would also like to add that people who are very persistence and do not let go have higher success rates (talking from my experience!)
Source: How to fix a bug
Popularity: 2% [?]
Subscribe to the RSS Feed or by Email and receive free daily updates
