I came across this article from back in January by Elliotte Harold regarding Subversion. Subversion is being adopted by more and more developers in recent times as their SCM tool of choice. I am using Subversion with my current Client and have found it great to work with. I have used a few of the SVN plugins to get my ENV working on my windows box but found the Subclipse plugin for Eclipse to be one of the better ones. This is also the one that Harold discusses in his article. He concludes his article as follows:
For internal repositories, Subversion is a vast improvement over CVS. Once some kind of obliteration functionality is added, it should be suitable for external repositories as well. While third-party Subversion support in tools like Eclipse is not quite as widespread as support for CVS, this is changing rapidly. Subversion should be the default source code repository for new projects…
…….The future lies with Subversion.
In the past I have used CVS and VSS but I have found Subversion has picked up where CVS has left off. I agree with Harold that Subversion is a must for any new projects.

I came across this 
So what are Code Reviews?
I became interested in code reviews while working with Accenture Ireland. As part of my role I was responsible for introducing code reviews into the project and insuring that they took place. It was amazing to see the difference a 15 minute discussion of a piece of code or a design document could improve the overall quality of the project. As more people are aware of the design for an early stage. It also serves to educate more junior developers on the team. Srivaths Sankaran presents a good overview of code reviews in this article. It will give you a good background in to why we perform Code reviews and the many aspect of a code review. He concludes his article by saying:
One piece of advice I would say is to remember that the primary goal of Code reviews is to improve quality and educate developers. It is not a witch hunt!