Subj : Not debugging? (was: How much should I charge for fixed-price ...)
To   : comp.programming,comp.lang.java.programmer,comp.lang.lisp
From : rem642b
Date : Tue Aug 23 2005 03:53 pm

> From: "Phlip" <phlip...@yahoo.com>
> The hirers are sick and tired of only getting kiddies who know .NET
> but don't know how to think to avoid debugging.

I suppose it depends on what you consider "debugging". I write a line
of code and immediately apply it to the data I have to see if it gives
the data I want. If not, I change that line of code. If it works, I
move on to writing the next line of code. When I get to the end of the
function I'm working on, I put all those lines together and unit-test
the entire function on the data I was just using and any other cases
that are useful to make sure it really works correctly in all cases.
You consider that not to be debugging, correct? What do you call it then?

.