Kasia has been trying out code reviews/pair programming at her work and I do tend to agree that code reviews should be done and that they probably result in better code, i.e. code that is less full of bugs We don’t do much code review either at work and after reading her entry it got me thinking that perhaps we should.
When 2 developers at least are working on 2 sides of the same problem I tend to think that pair programming could be very useful. Personally it sometimes does get on my nerves, especially when we are talking about the same thing but thinking about it differently, or there is a subtle difference in what we are actually talking about.
In the end, though it does tend to keep people focused on the task at hand and forces us to quickly work out a solution or pull each others hair out