On Sunday 04 June 2006 01:55 pm, 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 you go. I write code mostly in order to understand a problem. A fellow asked me the other day, "Why are you coding? We don't understand the problem yet. We have no specs." I said, "That is why I am coding. I use code the way I use a pencil with a good eraser." Increasingly my favorite tools are a spiral bound engineering notebook with a grid of 5 squares/inch, a number 2 pencil and a safety razor blade to keep it sharp. And vi and code. The code to do repetitive things and calculations ... Once I have something figured out it is usually time for me to find a real engineer and get them to do the hard work that follows. Programming encompasses such a wide range of tasks it is not surprising that there is no one approach fits all. BobLQ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
