This is also basically the standard critique of pair programming, but I&#x27;ve never heard it come from somebody who has done much pair programming. I&#x27;ve never tried mob programming myself, but I&#x27;ve done a ton of pairing, so I wouldn&#x27;t be averse to trying this on occasion.<p>The hard thing about making software is not the typing, it&#x27;s the thinking. And on teams, some of that thinking can be individual, but a lot of it has to be collaborative if the software is to end up having any real coherence. As Kent Beck writes, &quot;division of labor is a dangerous fiction when all of your big problems are integration problems&quot;.<p>I&#x27;ve done a lot of good work alone in long, focused sessions. But I&#x27;ve done even better work in long, focused sessions together. Hands down the best code bases I&#x27;ve worked on are the ones where we did it all using pair programming while changing pairs every half-day or so.