Why you need (sub)version control
I’ve been meaning to write about version control for a while, its seen to be an incredibly boring and geeky subject. I started using it for my dissertation project in my final year - and now I’m using it for almost every document, script or spreadsheet I have. I think that not oly can anyone use subversion, most people should use it!
I like using it so much I’ve started to get interested in the stuff behind the scenes, the stuff that makes it work - and how that can be used to improve it. So much so I’ve setup a subversion server with plans to start selling it. Free, time unlimited, trials will be available.
So, why is it so good and how can you use it?
Well, assuming you use a repository that’s hosted on a different physical machine, the first advantage is an automatic backup. That’s a plus, but not the main event - let me explain how it works. Every time you ‘check-in’ your work subversion notes the changes that were made from the previous revision and remembers that. So you can go back and see all of the previous versions - and what was changed in each version.
This really comes into its own when you figure out that last Friday you deleted a paragraph that you just realised you want to keep. You can simply view the version before that paragraph was removed and get it back.
There is a lot more to subversion that that, especially when you get more than one person working on the same thing. But I really think if you have the tiniest inkling that subversion might be interesting then give it a go!
If you fancy giving subversion a go then you’ll definitely need TortoiseSVN, if you can’t find anyone offering a free trial repository then drop me a line. I’m working on a web client for managing subversion repositories so testers are needed!
I’m trying to find a decent beginners tutorial to TortoiseSVN - but not having much luck so watch this space.