loading...
Version Control Systems
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2005.140September/October 2005 (vol. 22 no. 5) pp. 108-109
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Diomidis Spinellis, Athens University of Economics and Business
Sane programmers don't write production code without the help of an editor and an interpreter or a compiler, yet many software projects limp along without using a version control system. We can explain this contrast if we think in terms of the increased start-up costs and delayed gratification associated with adopting a VCS. We humans typically discount the future, and therefore implementing version control in a project appears to be a fight against human nature. It's true that you can't beat the productivity boost that compilers and editors provide, but four decades after punched-card programming in assembly language has gone out of fashion we must now look elsewhere for our next efficiency gains. And if you or your project isn't using a VCS, adopting one might well be the single most important tooling improvement you can undertake.
Index Terms:
version control system, VCS, configuration management
Citation:
Diomidis Spinellis, "Version Control Systems," IEEE Software, vol. 22, no. 5, pp. 108-109, Sep./Oct. 2005, doi:10.1109/MS.2005.140
Usage of this product signifies your acceptance of the Terms of Use.