The 9 rules of debugging
•
1 like•466 views
The document outlines 9 indispensable debugging rules: 1. Understand the system thoroughly as this is the most important rule for debugging. 2. Understand how the system works as debugging is difficult without this knowledge. 3. Methodically eliminate potential reasons for failures instead of speculating on many possible causes to find the actual cause.
Report
Share
The 9 rules of debugging
- 2. THE 9 INDISPENSABLE DEBUGGING RULES THOMAS PIERRAIN DAVE AGANS
- 3. UNDERSTAND THE SYSTEM 1. “This is the first rule because it's the most important. Understand?”
- 5. 2. “It seems easy, but if you don't do it, debugging is hard.”
- 6. 2.
- 7. 3. “You can think up thousands of possible reasons for a failure. You can see only the actual cause.”
- 8. 3.
- 9. 4. “It's hard for a bug to keep hiding when its hiding place keeps getting cut in half.”
- 10. 4.
- 11. 5. “You need some predictability in your life. Remove the changes that didn't do what you expected. They probably did something you didn't expect.”
- 12. 5.
- 13. 6. “Better yet, don't remember ‘Keep an Audit Trail’ Write down ‘Keep an Audit Trail ’ ”
- 14. 6.
- 15. 7. “Obvious assumptions are often wrong. And to rub it in, assumption bugs are usually the easiest to fix.”
- 16. 7.
- 17. 8. “You need to take a break and get some coffee, anyway.”
- 18. 8.
- 19. 9. “And now that you have all these techniques, there's no excuse for leaving it unfixed.”
- 20. 9.
- 22. 9