[Yacoby]

I think you need either code reviews or pair programming to ensure quality and bring developers up to a more even standard.

However I am not as fond of pair programming for ensuring quality of a change. I find that often it is easy when pair programming to go down the route that looks good at the time and it is hard to step back and evaluate the whole change. Where as being able to look at the end result without any intermediate steps often makes it easier to find flaws.

I think that with code reviews, I find them easier to do if I view the coder as an adversary. They have produced flaws and I need to find them.