>The output of pair programming must be greater than 2x the output of a single programmer to make sense.
IME it does. Most of coding is identifying problems and two sets of eyes lets you hone in on the problems quicker.
With design, two sets of eyes spots things that you will otherwise miss.
Programming isnt chopping wood. If you're experience with it is that you're bashing out code like you're on a factory production line then something has gone wrong.
>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.
I've never seen this happen once. If somebody managed to write docs that correctly anticipated every potential question I'd be very surprised.
IME it does. Most of coding is identifying problems and two sets of eyes lets you hone in on the problems quicker.
With design, two sets of eyes spots things that you will otherwise miss.
Programming isnt chopping wood. If you're experience with it is that you're bashing out code like you're on a factory production line then something has gone wrong.
>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.
I've never seen this happen once. If somebody managed to write docs that correctly anticipated every potential question I'd be very surprised.