A variety of influences tonight pointed me towards my earliest published article, for MacTech, in 1999 or so:
I was really just a kid. But I had learned an awful lot about debugging, thanks to my awesome job in the Apple system integration team. I guess that made me feel pretty confident about writing an article – for a real magazine, even. So what if hundreds or thousands of other developers knew more than I did about software development, I knew a lot about debugging! I had spent a few years testing and then developing the Mac OS system file (and system enabler), and was confident that few would be as up-to-date with MacsBug as I was.
Debugging is a skill I have kept throughout my professional career. If you’ve got a bug, chances are I can help you get to the bottom of it. I’m effing good at that. The fact that I can write code is somewhat incidental, because my primary skill is as a debugger.
This is especially handy when I’m debugging my own code, because I’ve got the bug writer and the bug buster within easy reach :)
The MacTech article is antiquated – depressingly so – but many of the concepts still apply to OS X debugging. If you’re at a loss for how to approach buggy code in your project, my old 20-something article might actually be of some use to you.
When it comes to debugging, some things never change.