3 ms·
"We understand pair brainstorming. We understand pair bicycle repair. We understand pair driving in rally racing. But we don’t understand pair programming?" We
by kstenerud 14y ago
"We understand pair brainstorming. We understand pair bicycle repair. We understand pair driving in rally racing. But we don’t understand pair programming?"
We understand pair painting. We understand pair music composition. We understand pair writing. We understand pair knitting. But we don't understand pair programming?
There is a time to pair up, and there is a time to isolate oneself and think and meditate and explore the problem space and be creative. Beware of those who espouse a one-size-fits-all solution.
- alekseyk 14y agoI 100% agree with you, to compare programming to 'bicycle repair' is a new kind of stupid, unless you both pair programming a hello world application.
- quanticle 14y agoEven his other examples don't make sense. I don't know if he's actually talked to musicians or writers, but I would be willing to bet that many of them actually don't work in pairs. Musicians may play as a group, but composition, as far as I can tell, is a fairly solitary activity. In the same manner, writing is fairly solitary, even though editing and review are social. To translate this into programming, I'd say that programming should be solitary while code reviews should be done in pairs. EDIT: Even the rally driving example doesn't make sense. In rally driving, there is a driver and there is a navigator. The roles are different and very clearly defined from one another. This is nothing like pair-programming, where the distinction in roles between the person at the keyboard and the person watching is much looser and the two people are expected to take turns at the helm.