Developer Testing, discussions about best practices: "Was there any way they could get a quick sanity check on code without having to wait an hour? The solution was to install CruiseControl on a second machine and create a new Ant target that just pulls the changes, compiles all the code, and runs our smoke tests. This cycle typically takes about 2 minutes, meaning that after a check-in the developer can expect email reassurance (or blame) in their inbox in under 5 minutes. "