But that's conditional on everybody not being jerks. Anybody who tries to score points by pointing out weaknesses is toxic to open and honest collaboration.
This is a totally personal problem, and I've had pretty long successful periods of my career that I've pair programmed most hours of most days, and I do think it's a technique with a lot of advantages, but it really isn't my favorite thing to do because of this kind of dynamic.
probably well intended, but no.
Some people are afraid of conflict and would rather agree when they really don't, some other people are just looking to "win" or always poke holes at everything but their own takes, both types aren't very useful in the end.
In my experience, when you find that sweet spot with someone who complements you, pairing up is just the best, definitely more than the sum of our parts.
This isn’t the best way to put it, but for lack of better words just starting with the mentality of admitting that it’s ok not to know what to do next and that we’re here to solve it really helps fight the kind of bias the article talks about.
It’s when you get to the point that you’re comfortable just reasoning aloud that the beauty of pair programming comes to light. Silly mistakes happen constantly but they’re caught right away and you move on so quickly in your shared state of excitement that a lot of the inhibition just goes out the window.
Mileage varies though, as not everyone gets the same benefits that I described.