Except that the points aren't really addressed. The article argues in favor of "code reviews, design reviews, and general documentation" but it totally avoids

Except that the points aren't really addressed. The article argues in favor of "code reviews, design reviews, and general documentation" but it totally avoids discussing the merits and disadvantages of them. It's not only pair programming that has pro and cons, and so using a different process (or more likely, a mix of different processes) always implies a tradeoff.