I assume you mean this part: > While pair programming might achieve some goals as a pedagogical tool, there are more time and cost efficient ways to share know

I assume you mean this part: > While pair programming might achieve some goals as a pedagogical tool, there are more time and cost efficient ways to share knowledge between team members. It's a very hand-wavey dismissal - "yeah, that doesn't work... NEXT!". I've enjoyed both sides of the learning process in pair programming and implying that documentation can cover everything that can be learned like that is, in my experience at least, laughable. It's not just about code, it's about the whole process, including other tools you might use, where and how to find things, etc. Engineers have different backgrounds that might've taught them different ways of approaching certain tasks. Some of those might stick