Earlier quoted context omitted.
When I first started pair programming, I found the most important part was even if I had a solution that would work, if I couldn't explain it to my partner, it was not a very good solution. Being able to convey an idea often forces it to be closer to the simplest and most comprehensible version of that idea.
> ...if I couldn't explain it to my partner, it was not a very good solution. I've found that in situations like that, I just write out a prototype and that clears up the confusion. Usually, what I'm trying to explain is good, but there's some context that I can't get out of my head and into theirs that's critical to understanding the thing I'm trying to explain.
Since I was using higher-order programming to control dispatch of various business rules, and they were not familiar with higher-order programming at all, there was a bit of a communication barrier/learning barrier that needed traversal.