I am a software engineer, developer, and designer by trade. In my experience, I am especially good at debugging and that's probably because I spent a ridiculous amount of time doing it. You know how some people are obsessive about keeping a perfectly clean and orderly house? I am that way about my computer's operation. If I notice anything broken or simply not working the way I would expect it to, I will endlessly investigate until it is solved. Over the years this has meant that I've developed an oddly comprehensive knowledge of things that go wrong with computers. I have also, with a bit of introspection, worked up a theory to try to teach others how to get better at debugging in general. My hope for this blog, and this site in general, is to improve readers' debugging skills. If it accumulates interesting stories of my own and others' debugging travails along the way, so much the better.