You sound very similar to me and it took me a long time to finally get round to using version control. Let me just say this - it is completely worth it. It is not so much about being able to roll back (which is very handy nonetheless), but it forces you to think about what you are doing and to break your coding down into small bite-size chunks which in the long run is very beneficial. I think we can break your post down into two very simple statements: I need to synchronise my files between multiple PCs. I which to use simple version control (commits and rollbacks). For the first statement I would highly recommend DropBox. I use it between the 3 different PCs I tend to use and even on my iPhone. It is the most stable file synchronisation tool I have seen and is free up to a certain size (2GB last time I looked). Now you have your files synchronised, you could use any version control system you liked. For the second statement I would recommend msysgit (Git for Windows) with TortoiseGit to make it simpler. TortoiseGit gives you a right-click context menu so you do not need to learn any command line functions. It is not built into VS, but all you have to do is keep a windows explorer view of your project folder open so you can jump in there and run some git commands when required. It also gives you very clear icons of the status of all of your directories and files (committed, modified, added, etc.). This was the best article on Git I have read: http://nvie.com/posts/a-successful-git-branching-model/[^] Now it does talk about branching a lot (which you may not want to do at first - you may change your mind after reading it), but it also has the clearest diagrams showing how git works. Hopefully this will help your get your head round how it all fits together. TL;DR I recommend TortoiseGit with DropBox.

As someone who has also only recently moved over to source code control please take a look at: http://nvie.com/posts/a-successful-git-branching-model/[^] It was my "eureka moment" with git. I picked up the basic usage of git and other systems (such as svn) reasonably quickly, but found myself not able to get my head around when I should be commiting/merging/tagging etc. This article was a fantastic push in the right direction to not only finding out how to use git, but also why I should be using it. I use git with TortoiseGit alongside VS 2010.

I think you are being a touch harsh on regular expressions. In this case it is the complexity of the postcode system that is causing the complexity of the regular expression not the other way round. Compare it to the regular expression for US zip codes (apologies if this is not entirely correct - this was grabbed from a quick google):

^(\d{5})(-\d{4})?$

The problem is that here in the UK we use a complicated postcode system that is difficult to validate via regular expressions, but that is probably easier to read by the human eye. Plus, I would add that you have managed to validate the string in a single (albeit a very long one) line. That is a plus in my book. You could also use (again from wikipedia):

[A-Z]{1,2}[0-9R][0-9A-Z]? [0-9][ABD-HJLNP-UW-Z]{2}

as a simpler more readable alternative, but which will allow some non-existent codes that do fit the normal pattern.