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
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.
Debugging 501
In the past few posts, I have tried to outline some of the key "power moves" that separate top debuggers