The author doesn’t understand what pair programming is about. It’s not about efficiency. It’s about sharing knowledge. The best pair programming was when I arr

The author doesn’t understand what pair programming is about. It’s not about efficiency. It’s about sharing knowledge. The best pair programming was when I arrived on a new project and I paired on a big subproject with someone with domain experience. He could have done it way faster and I coul’ve worked on something easier. But in the end, I gained a lot of domain knowledge extremely fast, faster than any documentation would have allowed me to. That’s what pair programming is about.