Re:Agile: 5 years later and you're still doing it wrong
by MartinCron on Tuesday February 21, 2012 @07:39PM
(#3618700)
Two things cannot become one thing, if they are meaningful.
My understanding of it is that the intention isn't to combine the two things, it is to interlace them so the feedback loop between them is as tight and short as possible.
Note: I don't really care for pair programming except in short bursts.
When I read this, I thought, "this guy is selling something".
> It combines the code review and the code creation into one step -- brings the review as far forward as possible, so there's no wait.
The only programmers I know who half-heartedly believe that are trying to convince themselves of it in order to sell pairing to pointy-haired bosses. Two things cannot become one thing, if they are meaningful. If you make them one thing, it's because they aren't meaningful to you. In this case it's peer review, and I don't want what you're selling.