I don't agree with this. Usually, the typing does half the debugging for you and when you have a real bug (as in, the program does something but not what you intended), you debug at the reasoning level, not at the "is there an overflow here?" level.
That one needs to be framed on a wall.
I'm definitely in the first camp (think to program), and have no problem with paranoid type systems, and I seldom need a debugger. Now I understand why other people do.
The mantra "well typed programs can't go wrong" actually means "our well typed programs can't go wrong, or we are so screwed."