Here's the thing: Use the best tool for the job. Work smarter, not harder. I'm debugging something right now. I can use the rapid compile time of golang to do t

Here's the thing: Use the best tool for the job. Work smarter, not harder. I'm debugging something right now. I can use the rapid compile time of golang to do things like: change the binary format, so that I can trace what part of the buffer was written by which function invocation. I can also write very sophisticated conditional debugging that would be iffy on most debuggers, where the machine sifts through the possibilities for me. That "one weird trick" has earned me a reputation as a magic debugger multiple times. Sometimes, it's best to use a printf and spot the thing in the console, or to see what's going on with the data to gain a better understanding. Sometimes it's best to debug something to rapidly see a complex interaction firsthand. It's always good to be smart about using multiple tools creatively.