Extreme Programming Installed

Reference:
Extreme Programming Installed
Ron Jeffries, Ann Anderson, Chet Hendrickson
2000 Addison-Wesley

Chapter 13

Summary:

While coding, it is important to test code in bits and pieces as it is written instead of doing a big test at the end of the project.  Unit testing involves checking to see if input yields the expected output.

Discussion:

Unit testing certainly saves time in the long run, but it is always tempting to forgo intensive testing while coding.  Still, the testing a little bit at a time is far mor efficient than testing a huge block later.



Chapter 14

Summary:

When writing unit tests, it is best to start with little tests.  In addition, the intent behind code should be clear, as opposed to simply having an algorithm.

Discussion:

 Mostly just providing examples of concepts from the previous chapter.



Chapter 15

Summary:

 When working on a team, code management is very important.  A repository is a common structure used to manage code, but team members need to be careful that they don't mess up the code in the repository.

Discussion:

I've used SubVersion on several occasions, and it is certainly an overall boon to a team.  Everyone must know what they are doing though, or else they might commit erroneous changes to the repository and cause major headaches down the line.