The problem isn't pair programming, per se. It's the forced nature of it in many locations. Every line of code has to be written/modified in a pair. The iron

The problem isn't pair programming, per se. It's the forced nature of it in many locations. Every line of code has to be written/modified in a pair. The irony? Pair programming has become a dogmatic process over the needs of the individual developer in many locations, yet is still considered a core Agile technique. That just isn't right. Like the author, I'm more introverted. I prefer to code alone. Forced coding or working with others drains me. However, if assistance is needed--myself or others--I've no issues working in a temporary pair to solve a problem. Pair programming wasn't intended to be an iron dictate of "you must". It was intended to be a "it's ok to ask for help if you have a problem, because working software is the goal".