It seems a lot of people here are talking about debugging in the context of automated tests and manually stepping through debugger loops. For me debugging usua

It seems a lot of people here are talking about debugging in the context of automated tests and manually stepping through debugger loops. For me debugging usually means "figuring out why we had an outage." This means looking at: 1) application logs, 2) server metrics, and 3) source code associated with the failed applications. I recently had to ssh and run ngrep on 8(!) servers to see how groups of messages passed around and then look at timestamps to correlate what happened. It was very tedious. This could have been saved by better debug logging; we could have switched that on for 2 minutes, run the tests, and and the looked at everything in Logstash. When this happens, I end up spending a ton of time tracking down errors. On a bad week, this can be half my time. So to me, debugging is as much thinking about how you'll have to solve errors in the future and planning for it as it is writing unit tests and tweaking code.