Many programmers dread big projects, often for a whole host of reasons. However, one particular aspect to big projects can sometimes seem more unappealing than any other code organization. Six or seven software developers, two software architects, a lead architect, and client-side developers all working on the same project often represent a recipe for disaster.
Mercifully, code organization on big projects has been made much easier in recent years with the advent of readily available, straightforward version control software.
In this short appendix, you'll encounter the basic principles of version control and see how to organize a version control strategy for your project. Then, you'll learn how these principles are applied in the most popular version control software and how to choose which (if either) suits your project best.