3 ms·
Most of your response seems to be an off-topic rant against frameworks and new technology, and you're certainly not wrong on those points. But what I find inte
by tankbot 14y ago
Most of your response seems to be an off-topic rant against frameworks and new technology, and you're certainly not wrong on those points. But what I find interesting is the on-topic portion, where you basically say this:
"Social programming ideas are nuts." and then you follow that with "My company does collaboration wrong by saving it all until the very end of a project where it's too late."
The piece directly addresses this by stating that pair programming is trading a short-term cost (doubling up programmer resources on the project) for a long-term gain (far fewer errors, fixes and less review and deeper developer knowledge).
If pair programming meant you didn't have such painful, never-ending code reviews, would you still think it's such a horrible idea?
- geophile 14y agoYes, collaboration is necessary, and yes, my company is doing it wrong. My preference would be to hash out a design earlier, before there is any code, rather than after the fact. Once you have code, you have wasted time, and it is often difficult to separate out ideas from implementation. And yes, for me personally, pair programming is a horrible idea no matter what. Pair programming vs. code reviews is a false choice. Ideal for me is design up front, away from the keyboard, and then everyone goes off, by themselves, and does their thing. Or in pairs, if that works for both of them.