Man I'm glad you said that! I was doing what you are doing but never quite articulated or justified it to myself.
cs On Sun, Jun 04, 2006 at 01:55:10PM -0700, Andrew Lentvorski wrote: > James G. Sack (jim) wrote: > >It's remarkable: once you become addicted to test driven development, > >your code structure seems to change (improve!) just by thinking in > >advance "how will I write a test for this feature/behavior". > > I *hate* test driven development. > > I write code to solve the problem *first*. Normally this is because I > don't quite know what the problem is or how to solve it. I don't tend > to write code that solves "CRUD" problems. My code tends to be technical. > > Now, once I have something which is working, I start to put the test > skeletons around it for debugging. > > I find this is a balance. Tests before stability are pretty much wasted > code. Once a section goes stable, then I tend to start doing tests. > Once I hit debugging, no bug gets fixed without tests getting added. > > -a > > > -- > [email protected] > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
