Some of my best code has been written with pair programming but I can see the flip-side. There's no day-dreaming, there's no zoning out, complete engagement all day long.
It's the same mental overhead as with taking care of toddlers; you have to be constantly aware otherwise suffer the consequences.. :)
Our normal thing is to form joint teams of Pivotal and client developers, and in that situation, pairing is also a really good way to teach the clients our way of doing things.
Of course, a team like that needs to only hire people who are up for that lifestyle.
You probably still wouldn't like it much, sadly!
One of the parts of my job that I dislike is watching people mouse around on the screen and try to type.
There's something so frustrating about tracking someone else's mouse movements and typing and the impotent watching when you know where they're meant to click or what they're trying to type, but seeing them flail around, that I find very unpleasant.
Also deflecting people's ideas I would find very tiring, having to explain why you don't want to do something you know is a bad idea, or explain why something you want to do is a good idea. Much more efficient to just do it in the best way you can think of, then have a code review later.
Seems like a waste of resources to limit two people to doing the one job.
That's especially true on those occasions that you do something nobody believes is possible.
And I actually like pair-programming, some of my best code was written with somebody sitting besides me and we have solved some really tricky bugs like this.
But we tend to do this only rarely. Most of my day is spent organizing stuff and reading emails anyway :-)