> Code reviews prevent this as well, without all the overhead incurred by pair programming.
I'm a big believer in correcting errant behavior in the moment. Simply the presence of an overseer can coerce a developer to avoid taking shortcuts with the hope that it might go overlooked in an asynchronous code review.
I am on a team of two, and yet, I rarely have time to audit code that my fellow has written, simply because the rest of the day demands other tasks to be focused upon
I think pair programming has its uses, but unless the 2 working together are on the same level it's really hard to get into "flow".