Ionrock Dot Org

My last semester I got pretty serious about using a versioning system. My software of choice was subversion. I tried arch for a while but I found it extremely difficult to integrate into my workflow. I am sure with enough work I could have gotten used to it, but I was not willing to lose productivity when other tools were available. I am convinced thought that had I stuck with it, I would have become a arch zealot. Its design is really nice and the paradigm it takes seems very logical and extremely helpful. Unfortunately, it wasn't practical for me.

With arch out the window and the masses consistently complaining that CVS is crappy, I started working with subversion. It was still very hard to get in the habit of working with subversion but overall it became rather nice. The biggest boon was that I could check things out on whatever machine I was on, work and check changes in. Of course this is the obvious benefit of a versioning system, but after trying many other systems of keeping a central workspace, this worked very well.

Now that I am working and using CVS every day, I am glad I took the time to learn what I have. I haven't really seen the difference between CVS and subversion but I have "felt" the differences. CVS "feels" kludgy and unstable. I know our sys admin is not a fan so it might be an administration issue, but overall, subversion just seemed easier to use. Of course beggars can't be choosers, so I will continue to get into the CVS groove as much as I can and wait patiently for the sys admin to migrate to subversion (which is in the works I understand).

I usually get along well with others... even CVS.