Version Control Before Git with CVS
I started my software engineer using CVS. I was using CVS as recently as 2014.<p>Why? Two reasons. I&#x27;d played with git but hadn&#x27;t really understood the power of trivial branching (though I was one of those CVS power users who could branch, but tended to use my IDE to manage it). I remember thinking to myself, oh this is like CVS, because that is how I used it when I played with it.<p>The bigger reason is that I was managing a team of 2-4 developers that rarely worked on the same thing. We all worked in the same room. The codebase was relatively small (35k loc). I could see no good reason to make the change when CVS was &quot;good enough&quot;. I was the same reason we used the same old crufty bug tracker--too many features to write to spend time upgrading infrastructure. Unless it was a 2x efficacy improvement; we did add automated testing and scripting around deploys because the benefits were obvious.<p>Now I love git and the power to branch and stage commits but I am still not sure it&#x27;s needed for colocated teams of that size.