For example, if a developer checks in code that does not compile, the nightly builds (as well as frustrated group members) will constantly remind him of this problem; generally, that developer will then either decide to use the available resources to improve his coding habits or leave the group. Nightly builds also help enforce common working hours (which, as I will discuss next month, help hold group culture together): Because nightly builds need to begin at a certain predetermined time, all developers who want their code incorporated into the build need to check in their code before that time and generally go home before the build begins.

-- Adam Kolawa is co-founder and CEO of Parasoft, a vendor of automated error-prevention software and services based in California. Co-author of Bulletproofing Web Applications (Hungry Minds, 2001), Kolawa has contributed to and written more than 200 commentary pieces and technical articles for numerous publications. He holds a Ph.D. in theoretical physics from the California Institute of Technology.