Heh, yeah, that approach sounds pretty terrible to deal with. What I do is extensive unit tests and useful logging. Unit tests catch most of the stupid stuff and plenty of the sophisticated stuff (and are a useful thing to have for a lot of other reasons anyway). Logging lets me track down what slips through the cracks. Most of the bugs that resulted in serous production issues for me were a result of rather complex interactions between complex components, not something a debugger would have helped anyone with.

That said, I have no doubt that there are a plenty of people who are amazing at writing code in VS and are much better developers than I am.