Suppose your project tests frantically, integrates continuously, and
releases easily.

Suppose then you hire a new coder, and need another workstation.

Then you have a party. All the source requires 3rd-party libraries, of
various versions, which must be matched, and these require configuration
options and scripts installed here there and everywhere. The project's
eldest guru must pair with the new guy, run the system over and over again,
diagnose each glitch, and reconfigure it away. This situation resembles
delaying integration long enough to encounter "integration hell". Instead of
smooth saling you get dominos of bugs.

Is this a process smell? Does it indicate someone should add a motherhood
story indicating the codebase is continuously outegratable? Would an
off-the-shelf configuration manager handle it? If so, wouldn't configuring
that tool be a chore each time the team changes a library?

(Cloning a dev machine's hard drive is cheating, and insecure.)

--
  Phlip
    http://www.xpsd.org/cgi-bin/wiki?TestFirstUserInterfaces