cooking up the offense like he's cooking ravioli

Version control software is a must for any developer. A few basic features that any good version control system should have include:

• Easy to use – shouldn’t get in the way of the developer
• View previous revisions – when something isn’t right you need to see how you got to that point
• Simple branching, tagging and merging abilities
• A server component for remote storage – a must for multi-member team development, but still very nice for ever a single developer

I have been using Subversion for version control for the last six years because it accomplished all the goals above. I wasn’t in the market for a new VCS when I happened upon Git and got excited again about version control.

I discovered Git through a coding community website called github. I started noticing that all the open source projects I followed and many of the new ones I stumbled upon were publicly sharing their source through github. github adds a social aspect to code development – it’s kind of like Facebook for developers – and as the name implies is centered around Git. Because of github, Git suddenly became cool and I had to switch.

After reading a few tutorials and getting the basics of Git down I saw the real power of switching to Git. Git makes branching and merging even easier than any of the other VCS I have used before. Even though I think backing code off your development machine is very important, I like that with Git you can create local branches without pushing those changes to the origin server. Fixing bugs and developing new code in their own branch is a best practice that is not often followed (at least by me) because of the steps involved – with Git those steps are too simple not to follow.

I still haven’t switched all my projects over to Git. I am mainly using Git for new projects. I still use SVN for Swap-bot, but as I become more familiar with Git I look forward to making the switch.