Git rules

Let me geek out for a moment to say how much I love working in Git. It’s a source code control system, used to track parts of a software development project and retain a history of every change made to every file. In any development environment, source control is absolutely essential, and in a team environment I think Git is the best choice.

For almost twenty years I used CVS for source control. It was great, and it seemed to do everything I needed. About a year and a half ago, a few guys on the Zing team started pushing pretty hard for us to switch to Git. We had a decade of code history in CVS, and I was really comfortable with it, so I was pretty resistant to the change. But finally I acquiesced (hey, what’s the point of having a really smart group of guys if I don’t listen to them?) and after a bit of a rocky start as I figured out how Git worked, I fell in love.

Now, as I sit here on Christmas Eve slamming out some code, I’m reminded of how awesome it is to be able to work on multiple code branches, hopping between them as I implement different features, and look at the complicated but detailed version history to figure out where something came from, and who wrote it.

Thanks, Linus, for making my development world a little brighter.

git