in reply to Programming strategy with no on-going testing

Do you lock yourself in a room and code till you finish, or do you ensure you have plenty of distractions in the way of cats and music and family, etc.?
Distractions? What for?
Do you go at it in one shot without getting up, or do you break it up into small phases?
And, most important, do you test as you go, or have you become so good that you don't make silly little mistakes such as misplacing punctuation and the like?
Test as you go by creating test scenarios to verify desired output. If you perceive that you would be wise to become more aware of the perils of punctuation in Perl programming, it is advisable to do so.
How do you write a lot of code while making sure that each smaller component piece is bullet-proof?
In practical application, the method of "test-driven" programming or whatever you want to call it is just the way you end up doing it when it has to get done.   To help figure out "what's right for you", ask yourself:   Would you compose a symphony (or even try to figure out how to play some catchy tune) without picking up an instrument to see if you're on the right track?

<reggae>The wise man build his house on the rock; the foolish man build his house on the sand </reggae> :-)
  • Comment on Re: Programming strategy with no on-going testing