"I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habit of depending on the debugger instead of on their brain."
Martin's essay reminded me of a fellow I worked for briefly early in my career. He wrote one of the first personal computer database packages (and became rather wealthy as a consequence). When I asked him about his work habits and philosophy, he told me that he'd single-stepped through every instruction in the application at least once. He also said that he didn't see how anyone who called themselves a professional wouldn't do the same.
I've though about that occassionaly over the past few years, as I've noticed that I'm getting a lot done without ever reaching for a debugger. Taking small steps and writing lots of unit tests helps a lot, even when working with languages that don't have safe pointers and built-in garbage collection. Writing the tests first as a way to develop testable APIs shakes out a lot of silliness before it has a change to grow into one of those "what in the heck was I thinking?!?" moments.