I used to work at a company where we did a lot of pair programming and enjoyed it a lot. As a fast touch typer I preferred to be the one at the keyboard. I som

I used to work at a company where we did a lot of pair programming and enjoyed it a lot. As a fast touch typer I preferred to be the one at the keyboard. I sometimes like to sketch things out first to test my initial idea. I think pair programming can be extremely effective and fun when done in an ambitious work environment with open minded people who can work well with others. I much prefer doing pair programming than not since it's an opportunity to discuss requirements/design/solutions and also a kind of code review before the actual code review. Coding on your own hides wrong assumptions, incorrect thinking, lack of teamwork/collaboration, misunderstandings and code quality issues which could likely to be found in pair programming sessions before a code review. It can be a great synergy when trying to solve complex problems where two people balance up different aspects of problem solving.