Shocks me that you're getting downvoted for this because that's exactly what the results would imply. Of course that's in regard to the Extreme Programming always on, constant pair programming approach. Pair programming isn't totally bad of course, and has its place, but yeah the results would seem to imply that consultancy-style (I'm looking at you, Pivotal) pair programming is a good way to produce reliably mediocre code with a body shop.
Ha! Field of software programmers act like a hive mind. People latch on to something and then it becomes their religion. Any criticism causes hurt feelings.
I've been programming for long time and have seen these trends come and go. Right from xml being the best thing since invention of wheel to micro services being elixir to all programming woes.
No, it's a good idea, but it's better in combination with solitary work.
Nope, it is an excellent idea. Just not all the time.
I enjoy pair programming on occasion, but I can imagine doing it all the time could be detrimental.