Source Control Management
Where I work, we have a full-time build engineer who manages and builds thousands of lines of code made by other people. It is an interesting and complicated process that will take you away from the low-levels of code and pit development skills into the deployment/version management process like creating branches, etc.
If you are thinking about CVS, you can go with Perforce (not free) which I heard is doing wonders. For my personal projects, I use Subversion (SVN) because of nice integration with Eclipse. Supposedly CVS is on it’s way out however it is the foundation repository of many companies today.
SVN has a very simple command-line interface which runs under *nix and has binaries for Windows. The docs for Subversion are some of the most concise, compact and simple reads I have enjoyed. They encourage you to read what you need to know and not everything from cover to cover.
SVN is not check-in/check-out like MS Visual SourceSafe. It is based on copy-modify-merge model of text files. There is also a capcity to lock files so that people cannot make overrwritting submissions. This is handy for binary files like .fla’s.
