Open Your Eyes
All problems have a solution. You may not see it yet, but the answer is there somewhere. You just have
Become a Toolmaker
In previous posts, I have discussed reducing a problem into its simplest form, and possibly even writing a representative executable
Debugger Tool Belt: BBEdit (...or whatever your favourite text editor is)
Understanding the debugging process deeply is the key to becoming a master debugger. However, any master debugger will have a
Pulling a Thread
As an elite debugger, you are conditioned to expect data that highlights a specific problem that needs to be resolved,
Swarming
While these posts have generally been about elevating your debugging abilities to Yoda-like stature, today I will like to riff
Patronus
The ELK stack is a very common way to collect, aggregate, and analyze log data. It is used by large
Debugging Fluency
In previous posts, I have stressed the importance of good logs, and of them being the cornerstone of effective debugging.
Sacred Cows
In an earlier post, I discussed the dangers of being wedded to your own ideas. I would like to riff
What's Changed?
To an observer who's go-to method of fixing things is "turn if off and then back on", software can seem