After much initial resistance, I've become a fan of pair programming. When things are clicking, ideas spark back and forth. Frames collide and interfere, bits of partial insight are exchanged, and you and your partner arrive at a solution that would have been impossible for either of you to get to working individually.
There is the famous psychological notion of flow. The thing is, this can happen among multiple people. Think of a lovely choir or orchestra. Or a basketball team where every team member just seems to be reading other team members' minds. The book (and presumably the upcoming movie) "The Boys in the Boat" really emphasizes this and crystallizes this.
As the linked article mentions, the author and his father butted heads for three hours because they were not listening to each other and pairing very effectively! Really good pairing does take work and practice. But when it starts to work there can be moments when it feels like magic. It is a great way to grapple with the myriad of unforeseen "details" that are actually life-or-death critical issues to project success.
There is the famous psychological notion of flow. The thing is, this can happen among multiple people. Think of a lovely choir or orchestra. Or a basketball team where every team member just seems to be reading other team members' minds. The book (and presumably the upcoming movie) "The Boys in the Boat" really emphasizes this and crystallizes this.
As the linked article mentions, the author and his father butted heads for three hours because they were not listening to each other and pairing very effectively! Really good pairing does take work and practice. But when it starts to work there can be moments when it feels like magic. It is a great way to grapple with the myriad of unforeseen "details" that are actually life-or-death critical issues to project success.