Move beyond mere source control to the problems source control doesn’t solve

If you’ve ever working on a multi-person development project that didn’t use some sort of source control system, you’re probably painfully aware of what it feels like to loose some of your hard earned work. Sure you may be able to reproduce the work but the feeling that you’ve already made the investment to create it once is very nagging.

Even if you’ve used source control systems you may have noticed that there are certain problems that a source control system doesn’t solve. Managing configuration files, consistency of file locations, standard coding practices, a check-in schedule, and a build process are all examples of application development problems that having a source control system with check-in and check-out won’t solve.