A systematic approach to debugging

from blog ntietz.com blog, | ↗ original
I've got a reputation at work as being a skilled debugger. It's a frequent occurrence that the weird stuff lands on my desk1 after it goes through another skilled engineer or two. To say my job is substantially "debug the weird shit" would not be an understatement and I'm here for it. This extends throughout our codebase, and into code I haven't...