Earlier quoted context omitted.
I also left a job due to pair programming. That company pair programmed 100% of the time. It concerns me that might become a norm. I wrote a blog post on why I think that's a bad idea: http://www.mattgreer.org/articles/pair-programming-is-not-a-...
I wonder if these kinds of teams are lead by extroverts, who appreciate having a captive audience for their peopley, extroverted shenaniagns. Having a stable of people who are contractually obligated to put up with their outgoing personalities.
The reality is, it will make the team produce fewer bugs. It will also help in knowledge sharing, and in some cases result in tidier designs.
But you'll basically have half the manpower. So unless you actually have serious problems with bugs, knowledge sharing, or code design, it's not going to be worth it. There are other ways to achieve quality, and most senior people can do that very well without someone pairing with them.