The unspoken rule is talking to the rubber duck :)
That is literally #8 in the list
Rule #10 - read everything twice
Debugging: Indispensable rules for finding even the most elusive problems (2004)
11–20 of 238 posts
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#12A good bug is the most fun thing about software development
Sometimes I am actually happy when there is a obvious bug. It is like solving a murder mystery.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#13Step 10, add the bug as a test to the CI to prevent regressions? Make sure the CI fails before the fix and works after the fix.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#14Make sure you're editing the correct file on the correct machine.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#15I also think it is worthwhile stepping thru working code with a debugger. The actual control flow reveals what is actually happening and will tell you how to improve the code. It is also a great way to demystify how other's code runs.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#16Make sure you're editing the correct file on the correct machine.
Poor Yorick!
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#17Personally, I’d start with divide and conquer.
If you’re working on a relevant code base chances are that you can’t learn all the API spec and documentation because it’s just too much.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#18I also think it is worthwhile stepping thru working code with a debugger. The actual control flow reveals what is actually happening and will tell you how to improve the code. It is also a great way to demystify how other's code runs.
I think that fits nicely under rule 1 ("Understand the system"). The rules aren't about tools and methods, they're about core tasks and the reason behind them.
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#19Personally, I’d start with divide and conquer. If you’re working on a relevant code base chances are that you can’t learn all the API spec and documentation because it’s just too much.
Also:
Fix every bug twice: Both the implementation and the “call site” — if at all possible
Re: Debugging: Indispensable rules for finding even the most elusive problems (2004)
#20Make sure you're editing the correct file on the correct machine.
Also that it's in the correct folder