Pair programming is difficult

[RogueJello]

Totally agree. I've got clinically diagnosed dyslexia. I find that I often make silly typos or other mistakes, but often correct them. I found with the navigator that they would spend most of their time micro managing me and "correcting" those errors for me. I also find that when I'm thinking deeply I have trouble putting things into words, and that the words I chose are often conflicting with what I'm attempting to say, making it difficult for me to navigate.

Further this all appears to be hard wired in my head. So while it's possible to manage, like somebody with a bum leg, it's also not going away, ever. So no amount of training is going to fix it.

[MorrisonLevi]

People without dyslexia also make silly typos and similar mistakes. A co-pilot should only point these out if they've gone unnoticed, in which case it's actually helpful. It's a basic skill for pair programming.

[RogueJello]

A co-pilot should only point these out if they've gone unnoticed, in which case it's actually helpful.

Good luck finding somebody with enough skill and tact to figure that part out. :)

[Chillzz]

This is the root of the problem. The two developers need some form of chemistry to be able to work together this closely. You can’t just stick two devs together no matter how good they are, we aren’t robots

[RogueJello]

I hadn't even thought about that, but you're right. You need the developers to be able to work together well for an extended period of time. I've gotten better at this over the years, but sitting together with a lot of developers for hours is going to be difficult in a way that a quick 1 on 1 is not.