Article (Carl Parrish)

[Carl Parrish]

Write the test first is a basic princple of XP. Once you get used to it
(and I admit it took me awhile) it cuts development time *way* down.
Because instead of writing what you think you need (then re writting)
your developing to your test. (now this does require that you get your
customer involved in your testing, but now you ask all the right
questions up front). 

Carl P. 


On Mon, 2002-10-07 at 13:05, Christopher Bardin wrote:
> 
> My reaction to the article on bowling score XP (Extreme Programming) was the confusion I usually feel after reading most things about programming.  However there is a reference in that article to another article:
> 
> http://areu.free.fr/BowlingGame.html
> 
> which could hardly be improved upon as a model for programmers.  I once read that you should "write the instruction manual first."  I haven't seen any improvement on that rule.  I am absolutely flummoxed by the tendency of programmers to and start coding with only the vaguest notion of what the program is meant to do, and no thought at all to the "typical" user.  This usually leads to little or no useful documentation and a user interface which is confusing at best.
> 
> Christopher Bardin
> 
> 
> 
> ---------------------------------
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos, & more
> faith.yahoo.com