[sirwolfgang]

The biggest problem I see with this is that your not really getting a second pair of eyes when you pair program. You almost get second eyes. Even if the person with you is 100% engaged the entire time, you end up syncing your thought patterns.

For example, I once worked with a teammate for 9 hours to write and debug a physics system. After all that time solving the problem with him, I was solving the problem like him. We ended up writing this 900-line solution to our simulation that kinda worked right most of the time.

I went home and laid down for 30 mins. During that mental reset, my mind turned to solving the problem with my method of thought. I ended up sitting up and grabbing my laptop and replacing all that code with a 30-line solution that worked 100% of the time.

Code review allows someone to come at a problem with a different perspective to find issues, not more of the same perspective.