Haha. Actually since most of my work these days is in javascript and using the dojo framework I constantly do console.log() into firebug. One of the cool things with dojo, and javascript's object literal syntax is that passing an object as an argument into console.log lets you navigate through the object's property tree. Saved me a bunch of time when trying to work out what the blazes I am getting back from different calls.
I still use a quick System.out.println on catalina sometimes just to see what different things are, since I only run jpda when I want to debug I use catalina.sh run which pumps out the catalina.out file into the terminal, so it can be faster during dev to stick a couple of System.out.println()s in there and see what comes out.
Horses for courses and all that. Though I think the author is arguing that you should re-read your code with a critical eye as it will pick up more flaws.
'Sworn to no party, and of no sect am I.' Frederick Vosper's republican motto.
I totally agree with the sentiment actually. I try to avoid the debugger; ideally I'll write a unit test. Just not using a logger, where you can therefore tune what comes out, seems crazy to me.
Give me utilitiy or give me something slightly better!
Comments