I've found it to be quite the opposite. It's also important to note that mob programming recommends rotating who is "driving" the session, so we change who is sharing every 15 minutes.
I don't think this approach scales to more than a team of 4-6 people but we've been able to forge strong bonds on our team, solve complex problems (in domain definition, actual code, ci/cd issues, and more) in ways that the entire team feels are appropriate and while also keeping the whole team abreast of all the changes. We get far more done than we used to and we've successfully onboarded several new team members.
I think the trick is that instances of
being stuck will tend to zero as you get more brainpower at the problem, or even the watchers spotting mistakes. And what I love about pairing is the code review comes for free. I hate being sent 1000 line change PRs blind :-0
I don't think this approach scales to more than a team of 4-6 people but we've been able to forge strong bonds on our team, solve complex problems (in domain definition, actual code, ci/cd issues, and more) in ways that the entire team feels are appropriate and while also keeping the whole team abreast of all the changes. We get far more done than we used to and we've successfully onboarded several new team members.