Revision Control Systems… avoid them or use them?

We use subversion a great deal but I don’t understand why there are people that refuse to use it.  The TechRepublic article, Avoid these six common development mistakes, sheds a bit of light:


4. Failing to see the value in a version control system

Most developers are all-too-familiar with this scenario: You roll out a new version of a critical Web application, and your cell phone rings constantly the next morning with cries of site problems.

As long as you’re willing to admit that you may have made a mistake or two, a version control system can be your best friend in this situation. By using version control systems, such as CVS, IBM Rational ClearCase, or Microsoft Visual SourceSafe, you can easily revert to the previous version of the application and move it to production. This gives you time to locate the problems within the development environment while the production site is readily available. This beats frantically searching through production code to locate the problem.

In addition, a source control system allows concurrent development so different team members may work with the same code. When the developers check their changes into the system, the changes are merged together.

One reason why some developers don’t like version control systems is because it adds a layer to the development process, which means the submission and retrieval of code to and from the source control system can be slow. This extra waiting time can tax the patience of some developers.
Read more…

Hmmm.  It might be more of a matter of convenience for some developers not to use or learn how to use a revision control system.  Looks like I’ll have to write a few wrappers to simplify it.

Share Button

Leave a Reply

Your email address will not be published. Required fields are marked *