Continuous Integration in XP
What mechanisms can a team use to prevent integration problems? Continue reading Continuous Integration in XP
Exploring Extreme Programming
What mechanisms can a team use to prevent integration problems? Continue reading Continuous Integration in XP
This exercise offers you a chance to practice test-first through a series of challenges. Each challenge provides a set of tests. Your job is to write code that supports the tests. Continue reading Test-First Challenge: Spreadsheet
Practice test-first programming Continue reading Stoplight: The Test/Code Cycle
Extreme Programmers write tests before they write the corresponding production code. In “test-first programming,” you start with a small test, then write just enough code to implement it, and continue with the next test until the code is done. Continue reading The Test-First Stoplight
A performance spike can give you crucial information about your system’s potential performance. Continue reading How Do You Do a Performance Spike?
Programming can be a performance art. Continue reading Programming as a Performance Art
Design patterns are interesting in themselves, but it’s useful to be able to move between patterns while refactoring a system. We’ll look at how you can move between command, interpreter, and visitor. Continue reading Command, Interpreter, Visitor
The XP Programmer’s Cube is an artifact that captures the key activities in a day in the life of an XP programmer. Continue reading XP Programmer’s Cube: A Day in the Life
An earlier refactoring example is taken further, introducing true templates and improving performance. Introduction This paper extends an earlier example of refactoring. (See “Refactoring: An Example” in Extreme Programming Explored) In that paper we refactored a Java program that was Continue reading Refactoring: An Example, Extended
Evolve from nothing, to an item, a collection, and a composite, or back again. Continue reading From 0 to Composite (and Back Again)