@RecursiveNeuron Except for a fraction of particular types of cases, such as realtime or embeddded, if you can't quickly and easily debug with print statements then your *design* is the main problem.

@davidr @RecursiveNeuron this this this.

Personally, I debug with print statements *in the tests*. Why would I need a debugger?

@RecursiveNeuron Well, I'm using #Java and #SLF4J but this is effectively the same as printf: writing information to the console (on the test environment only). Makes the console tell a story, so you can see where, when, and how your specific logic came off the rails. Using the IDE debugger feels more like taking a magnifying glass to a single grain of sand, but having no idea how it fits into the rest of the beach.