Fashionable == !quaint

Post #279,496 by admin 3/25/07 12:55:37 PM Reply	Fashionable == !quaint You're the one using the words that way, not me. :-) I've never been one to use debuggers, and a live system isn't worth the hassle of repository-based development. When I do Django development I never have to restart the program either. To each his own. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #279,502 by tuberculosis 3/25/07 1:17:43 PM Reply	I code in the debugger then execute it, write, step, write, step.... Guarantee's a high level of quality. If I write a line wrong, I just back up the PC to the outer context, change the line, and test it. I recently had to fix a Java web service and felt absolutely crippled because I couldn't write a couple lines for the wacky string manipulation I was about to do - just to make sure I had it right. This is the way computers should work. I4 NOW! Impeach, Indict, Incarcerate, Inject Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice
Post #279,530 by admin 3/25/07 8:14:22 PM Reply	I prefer to use unit tests to guarantee quality They're repeatable and useful for regression testing. I don't have to worry about side effects, either. As far as immediate Java testing, that's what the Bean Shell is for. Or use the remote debugger if you want. Either way. Again, different strokes. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #279,568 by tuberculosis 3/26/07 2:04:26 AM Reply	I do both Cool thing about SUnit is you click on failed test - brings it up in a debugger - step, analyze, and fix. I4 NOW! Impeach, Indict, Incarcerate, Inject Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice

Welcome to IWETHEY!