There are good books about debugging, simple but effective.

https://www.amazon.ca/Debugging-Indispensable-Software-Hardw...

I recommend https://www.amazon.com.br/Debugging-Indispensable-Software-H...

It has concrete points to focus when debugging and a bunch of examples for each. And it's easy to read as an introduction to the subject.

Debugging is a valuable skill that some of us were lucky enough to pick up by chance. A friend recommended an excellent book that very nicely explains the process: "Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems"[1]. I found myself nodding along while reading. I think this would have been a hugely valuable primer if I had been exposed to it before I figured out how to do it on my own.

[1]: https://www.amazon.com/dp/B00PDDKQV2

Become an excellent debugger. It's sorely neglected as a skill that goes along with development, but is not the same thing as being a good coder.

Read this book: https://www.amazon.com/Debugging-Indispensable-Software-Hard...

It's short and sweet and applies to any technology problem.

> Learn how to debug

I recommend this book: http://www.amazon.com/Debugging-Indispensable-Software-Hardw...

Another great read for debugging that was recommended to me years ago:

http://www.amazon.com/Debugging-Indispensable-Software-Hardw...

I've read a number of books on debugging, it's something of an interest of mine. The best general-purpose debugging book I've read is the cumbersomely named

Debugging: The 9 Indispensible Rules for Finding Even the Most Elusive Software and Hardware Problems by David J. Agans

Amazon link: http://www.amazon.com/Debugging-Indispensable-Software-Hardw...

What I really like about it is that it gives a number of high-level approaches to solving debugging problems and is written very accessibly.

I wonder if you have much to add to http://www.amazon.com/Debugging-Indispensable-Software-Hardw... (which I really like).

Rule 5: "Quit thinking and look" is (I think) equivalent to your "don't assume".

Rule 6: "Divide and Conquer".