I worked at a software company where we did pair programming and test first 100% of the time. We shipped amazing code in timeframes I wouldn't have believed possible for system than could handle scale unheard of at the time (think of the datacenters powering Walmart). All I can say is this guy has some valid points even though I remain a huge advocate of this process. While I loved my time at this place, I had to quit after 3 years because of burn out.

The trick is to have a way for developers to power down somewhat. I'm not sure how you would do that. I never got the chance to figure it out.