I have done some pair programming. At my first job we sometimes did it when some problem proved especially tricky. Typically a tricky bug. In some cases it's i

I have done some pair programming. At my first job we sometimes did it when some problem proved especially tricky. Typically a tricky bug. In some cases it's invaluable, absolutely. I just don't think that's a large percentage of the code written on a daily basis. For most tasks pairing seems to be either 1) one person tapping out simple code which practically writes itself while the other lazily nods along. 2) One person solving something tricky which happens to be their area of expertise while the other stares blankly. Maybe at that point it would be useful to explain things in detail, but that can make development take much longer and if something like this requires rethinking halfway it can be quite taxing. In that case, I would prefer waiting until it's done and compiling the result as an annotated review. Which can be a great forum for asking questions.