Constant refactoring (i.e. constant tweaking and improving of your code) creates an unnecessary overhead. Outside the XP world, occasional refactoring is welcome, as it is useful to check and improve ('de-fluff') your design; but constant refactoring makes no sense. In fact it only makes sense in the XP world, where the design is made up as you go along.
Sunday, September 12, 2010
Extreme Programming Dangers
While doing some online research on development methodologies, I came across a useful analysis of how Extreme Programming (XP) can break down in real life, because each component methodology (lack of fixed design, pair programming, constant refactoring) is too dependent on the others for success. An example:
Subscribe to:
Post Comments (Atom)
estimated 9 million out LGBT people in the US alone. That estimate reflects only a slightly less thคาสิโนออนไลน์an 4% of the entire population, yet we hear that more than 9% of the population is actually gay. Our community is still struggling for equal rights, to marry legally, to be out without discrimination and all the other legal rights afforded to straight people.
ReplyDelete