Frank W. Zammetti asked: > netsql wrote: > > PS: Debug is for corporate newbies. Pros don't waste time on this, > > they > > do this new thing called unit testing ;-). Realy, when > somone on my team > > is in debuger, I pull them in my office, and required that > they improve > > test coverage more granular and more layers of > indircection. Debuging is > > a sign of low productivity in my book. > > Wow, now we can get into a debugging vs. not debugging argument :) LOL > > Wait... Vic, were you actually serious, or was that paragraph > meant as a > joke? I actually can't tell right now :)
FWIW, I agree with Vic. Once you get "test infected" and write your code using TDD, there's very little need for a debugger or for debug-level log statements. And the resulting unit tests continue to help, even as you move on to other parts of the code, unlike walking through your code in a debugger or log file. As a result, productivity quickly goes up. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
