Anonymous
Unregistered
|
|
Extreme Programming is a fancy way to say "Common Sense." None of these techniques are new. If you have smart leaders showing the way, all the XP concepts are there...minus the author-speak of course.
|
**DONOTDELETE**
|
|
You are 100% correct, practices of XP are not new. Infact some of them date back to the 70's. However, the combination of the practices: The Planning Game, Continuous Integration, Unit Testing, etc creates a "unique" methodology. The interplay between the practices is where XP takes a step away from "commmon sense". I'd encourage you to read a bit more about XP, there are some subtle points that are perhaps not so obvious. Thanks for the post!
--Ryan
|
Anonymous
Unregistered
|
|
I agree. But without understanding extreme programming well, some people just mis-interpret extreme programming as sloppy programming. Go like hell, and don't look back. This is a gross mis-interpretation of extreme XP and one I feel is easy to fall into if you don't understand its nuances.
|
Anonymous
Unregistered
|
|
I don't know how anybody who has even breifly looked at the XP ideal could even suggest that it could promote sloppy coding.
In XP you break the entire project into tiny little peices, and just code those, in pairs and you write a automated test for that method/function before you actualy code it.
With its drive towards writing code readable for not only your pair by for your whole team, provable tests and the most important features first the only thing that comes out of a team that implements XP well is good code.
So I would say that the only people who would assume what you state, are people who haven't actualy read anything on xp.
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
