3. The point of a code retreat is not to make
progress on the problem. The point is to
write perfect code!
Corey Haines
4. In each session...
1. Set a goal
2. Try to reach it
3. Destroy your code
4. Retrospect
5. Pair Programming
• Talk about your assumptions, short-term
goals, general direction
• Switch roles frequently
• Communication: "This method is too long"
vs "Could we make this method shorter?"
• Exercise: Ping-Pong-Pairing - one person
writes a test, the other tries to fix it.
more http://jamesshore.com/Agile-Book/pair_programming.html
25. TDD as if you meant it
• Write one failing test
• Make the test pass by writing implementation code in the test
• Create a new implementation method/function by:
• extract method on implementation code from (2), or
• moving implementation code from (2) into an existing method
• Only ever create new methods in the test class
• Only ever create implementation classes to provide a destination
for extracting a method created as per (4).
• Populate implementation classes by moving methods from a test
class
• Refactor