This section is a combination of things we have learned in this chapter and best practices typically associated with software development in a team environment and with the help of Subversion.
Use the convention of organizing your code into three folders: "trunk", "branches", and "tags." Loosely coupled projects should get their own structure; whereas tightly coupled projects can share the same folder threesome.
Commit and update often. Many small conflict resolution cycles are usually much easier than having to resolve major conflicts at the end of your tasks development cycle. Frequently committing your code also serves as a backup. As a rule of thumb, commit your code before you call it a day and preferably also before you take lunch. However, don't commit code that will break existing functionality.
Write descriptive and informative commit comments. Reading commit comments is much faster than having to read multiple files of code when trying to...