First commit

703.html

@@ -0,0 +1,22 @@
+Part I Another Fine Mess You’ve Gotten Me Into (Laurel and Hardy Take Up Programming)<br />
+Chapter 1: XP in a Nuthouse (Oops, We Mean Nutshell)<br />
+Chapter 2: Where Did XP Come From? (Chrysler Knows<br />
+It Ain’t Easy . . .)<br />
+Chapter 3: The Case Against XP<br />
+Part II Social Aspects of XP (Mama Don’t Let Your Coders Grow Up to Be Cowboys) <br />
+Chapter 4: Extremo Culture<br />
+Chapter 5: The On-site Customer<br />
+Chapter 6: Pair Programming (Dear Uncle Joe, My Pair Programmer Has Halitosis) <br />
+Chapter 7: Oral Documentation (Oxymoronic, or Just Plain Moronic?)<br />
+Part III We Don’t Write Permanent Specs and Barely Do Any Upfront Design, So <br />
+Chapter 8: Design After First Testing<br />
+Chapter 9: Constant Refactoring After Programming (If It Ain’t Broke, Fix It Anyway) <br />
+Chapter 10: User Stories and Acceptance Tests <br />
+Part IV The Perpetual Coding Machine <br />
+Chapter 11: Software Is Never Done (The Schedule Does Not Exist Per Se)<br />
+Chapter 12: Emergent Architecture and Design <br />
+Chapter 13: Embracing Change (Embrace People, Manage Change)<br />
+Part V The Big Picture<br />
+Chapter 14: Scalability<br />
+Chapter 15: Refactoring XP<br />
+Chapter 16: Conclusion: Neutralizing the Reality Distortion Field

LICENSE.txt

@@ -0,0 +1,27 @@
+Freeware License, some rights reserved
+
+Copyright (c) 2003 Don Rosenberg and Matt Stephens
+
+Permission is hereby granted, free of charge, to anyone obtaining a copy 
+of this software and associated documentation files (the "Software"), 
+to work with the Software within the limits of freeware distribution and fair use. 
+This includes the rights to use, copy, and modify the Software for personal use. 
+Users are also allowed and encouraged to submit corrections and modifications 
+to the Software for the benefit of other users.
+
+It is not allowed to reuse,  modify, or redistribute the Software for 
+commercial use in any way, or for a user�s educational materials such as books 
+or blog articles without prior permission from the copyright holder. 
+
+The above copyright notice and this permission notice need to be included 
+in all copies or substantial portions of the software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS OR APRESS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+

README.md

@@ -0,0 +1,15 @@
+#Apress Source Code
+
+This repository accompanies [*Extreme Programming Refactored*](http://www.apress.com/9781590590966) by Don Rosenberg and Matt Stephens (Apress, 2003).
+
+![Cover image](9781590590966.jpg)
+
+Download the files as a zip using the green button, or clone the repository to your machine using Git.
+
+##Releases
+
+Release v1.0 corresponds to the code in the published book, without corrections or updates.
+
+##Contributions
+
+See the file Contributing.md for more information on how you can contribute to this repository.

contributing.md

@@ -0,0 +1,14 @@
+# Contributing to Apress Source Code
+
+Copyright for Apress source code belongs to the author(s). However, under fair use you are encouraged to fork and contribute minor corrections and updates for the benefit of the author(s) and other readers.
+
+## How to Contribute
+
+1. Make sure you have a GitHub account.
+2. Fork the repository for the relevant book.
+3. Create a new branch on which to make your change, e.g. 
+`git checkout -b my_code_contribution`
+4. Commit your change. Include a commit message describing the correction. Please note that if your commit message is not clear, the correction will not be accepted.
+5. Submit a pull request.
+
+Thank you for your contribution!