Gives an idea of what pair programming looks like when practiced properly.

Both approaches have their pros and cons of course. Whatever you pick, it has to start with a care for quality shared within the team.

A good in-depth article about pair programming. Shows well the pros and cons.

Developers tend to push for pair programming mostly for technical and code quality reasons. This is fine, but often the fact that it also spreads knowledge and ensures business continuity is forgotten.

Good criteria to decide to pair or not. This is still not practiced enough. Maybe knowing when it's best to reach out to pair will help get more into it.

Funny experiment. This shows what you can achieve in terms of teaching and learning during pair programming setups. Shadowing someone is a powerful approach.

Interesting take and theory about pair and mob programming. Indeed finding the right path to optimize a piece of code is likely harder in such setups.

This trend around critiquing code reviews on the argument of "trust" should be challenged indeed. This is just the wrong way to approach it.

Good balanced view about pair programming. I'd definitely like to practice it more, although whole days might be a bit too much and too exhausting.

Very thorough article with plenty of tips and ideas on how to run nice pair programming sessions.

Interesting coaching approach for teams. It's indeed hard to get teams to stick to some of the difficult development practices... By mixing several approaches, this looks like she's onto something here.

Like everything, Pair programming also has a dark side. It's obviously more potent if you do it too much.