[imiric]

> I do plenty of presenting at work, where I share my screen and write code, Twitch-style, for an audience of coworkers. I do this in order to convey material to a captive audience, not as a baseline method of doing work. “Teaching” and “programming” are two non-overlapping activities for me, as the communications aspect tends to overtake most of my mental capacity, leaving only a precious few cycles for problem solving and creativity.

Maybe the problem is that you're approaching it as "teaching" instead of working in close collaboration with other engineers to achieve a better solution to a problem than what you could've come up with on your own? You might be a senior, but there's always something to learn in how someone else approaches or thinks about a problem, and you're depriving yourself of the chance of becoming a better programmer if you reject this outright.

Pair programming is not for everyone, nor everyplace or time. Like most programming techniques it has its pros and cons and should be considered before adoption in a team, or worse, being forced into adoption. But it certainly has tangible benefits in sharing knowledge within a team quickly and achieving optimal solutions in a more immediate way than, say, a code review would.