In Perl, I knew conventions like ‘use strict’ and ‘use warnings’ which helped to keep code clean and maintainable and not fall into the little dynamic language gotcha’s. Even php had things like print_r() that could be used to see if the code was doing something unexpected.
The closet thing I have now is chrome’s debugger and metric engines, but every time I pull that up, I feel that its far too late in the process. I want the computer to be helping me code better WHILE I am coding, not forcing me to dive into all sorts of metrics after the fact.
also related: javscript and ruby ‘wat’
What other tricks can I use to avoid the living hell of “62dog” + 10 = 72 ?