"Ban the Debugger" was an unfortunate name for this post, because obviously debuggers are useful. Having worked in support, I always opened up a bug when log/c

"Ban the Debugger" was an unfortunate name for this post, because obviously debuggers are useful. Having worked in support, I always opened up a bug when log/console output was insufficient to pin down the problem a customer was having. The notion of (temporarily) banning the debugger seems great. I've seen some logging standards that you could follow, but the output still wouldn't be enough to nail down the cause of an error. If the failure of one test in (A && B && C) results in a single error, how were you supposed to know which of A/B/C caused the problem? So, yes please, have some failure cases setup ahead of time, and send the logs to the developers and see if they can figure out which failure mode it was without getting any live access to the program. But don't call it "banning their debugger." :-)