Quality assurance is always an issue in XP. Is it possible to subscribe to the XP tenets and still create code that stands up over time? Tell us about your experience; join the discussion.
Developers should be fully aware of the risks of the extreme programming methodology.
by Bruce Abbott
January 1, 2000
xtreme Programming (XP) is not some nerd bungee jumping off a bridge with a laptop. It is not a geek writing code while doing back flips on a skateboard. Nothing nearly so exciting. Extreme Programming is simply a software development methodology. I'm not saying that XPers are fanatical or cultish, but I bought my copy of "Extreme Programming Explained" (Addison Wesley Longman, 2000) by noted programmer and Smalltalk guru Kent Beck from a guy in an orange robe at the L.A. airport.
<
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
xtreme Programming (XP) is not some nerd bungee jumping off a bridge with a laptop. It is not a geek writing code while doing back flips on a skateboard. Nothing nearly so exciting. Extreme Programming is simply a software development methodology. I'm not saying that XPers are fanatical or cultish, but I bought my copy of "Extreme Programming Explained" (Addison Wesley Longman, 2000) by noted programmer and Smalltalk guru Kent Beck from a guy in an orange robe at the L.A. airport.
<
