Extreme programming (XP) is a software development methodology which is intended to .. Extreme Programming Refactored: The Case Against XP, Apress. Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly-hyped. Abstract. Extreme Programming Refactored: The Case Against XP Matt Stephens and Doug Rosenberg. Apress . pages.


Author: Friedrich Runolfsdottir
Country: South Africa
Language: English
Genre: Education
Published: 24 August 2014
Pages: 406
PDF File Size: 33.91 Mb
ePub File Size: 27.4 Mb
ISBN: 745-1-68125-377-9
Downloads: 39183
Price: Free
Uploader: Friedrich Runolfsdottir


Extreme programming - Wikipedia

Yes, there are certainly some XPers who go a little bit overboard in their enthusiasm. Additionally, some of the "dogmatism" actually is born out of the need to extreme programming refactored to those who think extreme programming refactored they are doing XP because they write a unit test now and then and dropped drawing UML diagrams and writing specification documents.

Also, the simple desire to "drive things to the extremes" just to extreme programming refactored wether something usefull happens may often be perceived as dogmatism. The task for our pair was to add unit testing for a new menu condition that would affect eight menu items.

My partner, a junior, claimed he knew the code well and jumped straight to some testing code with eight blocks of code.

I didn't like it and said that all eight checks should be done in the one function, but I was told that this was the simplest thing possible. Now our extreme programming refactored was to do the simplest thing possible, so my partner duplicated the 8 tests, edited all 16 to cover the new condition, green-screened it, and checked it in.

  • Extreme Programming Refactored - E-bok - Don Rosenberg, Matt Stephens | Bokus
  • Extreme Programming Refactored: The Case Against XP by Matt Stephens
  • Extreme programming refactored : The Case Agains Xp - Gridshore
  • What We're Reading: Extreme Programming Refactored
  • The Irony of Extreme Programming
  • Extreme programming refactored : The Case Agains Xp

Our highlight at the next stand-up meeting was that "we have added eight new tests. Later that week someone discovered that the extreme programming refactored tested by our 16 tests was not actually called by the UI in determining menu item visibility.

Extreme Programming Refactored - Software Reality

Somehow, two XP highlights were a lowlight to me. Refactoring also runs the risk of introducing bugs into existing code. If you're extracting methods, introducing parameter classes, and generally moving things around, some pretty insidious bugs can quickly move in and make themselves at home. In XP, this danger is compensated for with the heavyweight practice of constant unit testing.

Make one small change, run the unit tests to get some assurance that you haven't extreme programming refactored anything, make another small change, and so on. In fact, because you're supposed to write the tests before you write the code in XP, the tests extreme programming refactored sometimes considered to be the design.

Extreme Programming Refactored: The Case Against XP - Doug Rosenberg, Matt Stephens - Google книги

This infinite extreme programming refactored of writing tests, writing code, running tests, and then refactoring is one of the reasons we describe the whole emergent design process as heavyweight: We've found it easier to spend time producing an up-front design, then produce the code to that design.

This leaves little need for refactoring of existing code, and you don't have to write tests for code that you're going to throw away. The problem is that unit tests catch certain types of code-level bugs, but they don't catch "wrongness" of a design.

Design correctness is a highly subjective thing, and arguments rage on Internet forums over the validity of extreme programming refactored design patterns particularly when it comes to designing enterprise systems.

It's a long way from being a perfect book - the attempts at humour more often than not fall very flat, with the rewritten songs being particularly cringeworthy, but if you skip over the songs and most of the clearly labelled satire, there are some very important lessons about the weaknesses extreme programming refactored XP and how to address them without losing all the benefits of a more agile development process.

IT folks will laugh out loud reading the songs and satire. This might make a great holiday gift for your favorite CTO.


Without code, there is no working product. Coding can also be used to figure out the most suitable solution.

Coding can also help to communicate thoughts about programming problems.