RAX.IO 2019

Debugging systems should not be a burden, but by using 9 simple rules, regardless of the system, we'll be able to navigate through the problems and be able quickly recover from them. The rules of battle for tracking down hardware and software problems.

This is not a talk about debugging issues in specific programming languages, or how to solve problems in Linux.

This talk is meant to help change the way you think about debugging, making those pesky problems suddenly much easier to find and fix; explaining the logic you need in the real world, logic that is usually learned from years of experience

We will cover the following rules that aim to help us through problems:

* Understand the System
* Make it Fail
* Quit Thinking and Look
* Divide and Conquer
* Change One Thing at a Time
* Keep an Audit Trail
* Check the Plug
* Get a Fresh View
* If You Didn't Fix it, It Ain't Fixed