I don't see pair programming as a disruption to the individual mind of the single programmer. Then I believe something is wrong in culture of the organisation.

I don't see pair programming as a disruption to the individual mind of the single programmer. Then I believe something is wrong in culture of the organisation. It should definitely not be enforced but encouraged. The reasons I believe that is because the human psychology is also based around success and praise from our relations. The benefits you get from sharing thoughts and possible options to a challenge can hardly, imo, be bad. Pair programming has taken place in my career, in cultures that encourages a pace to get work done, in a manner where quality is measured by how well a team works together and how well the team is capable of understanding eachother - but as a team. I also believe that if you cannot explain in words, how you would go about solving a challenge, then it's premature to start coding on it. Then you are moving to fast. Pair programming is like any other thing. It should be applied when necessary and not be enforced on 80% of the work because it's perhaps only valid for the hard 20%. I have really thought about making a pair programming service for years, where people can connect and program as a pair, for the hard parts. Good discussion