3 ms·
I'm certainly not saying that XP and open source are the same model, but rather that one thing they have in common is improved code quality ("given enough eyeba
by gruseom 18y ago
I'm certainly not saying that XP and open source are the same model, but rather that one thing they have in common is improved code quality ("given enough eyeballs..."). Are you aware that pretty much the only definitively reproduced finding in the literature about software engineering is that code reviews and inspections reduce bugs? The trouble is that if you do them after the fact, they're expensive. Prohibitively expensive, in fact, for commercial projects, so nobody does them. Plus they degenerate into boring pro forma meetings. XP's answer to this is rather elegant and if anybody knows a better one I'd sure like to hear it.
"Collective code ownership" sounds like everybody's going to be forced onto a collective farm and made to slave in the fields and then sent to barracks where they each get a potato for dinner and all go to bed at the same time, and the government raises your children. So I'm not surprised you think that it means your code will be seized by the state and you will never be allowed to "see a feature from inception to completion". Some of XP's terminology and dogmatism kind of foster these reactions. I don't like it either. But your objections don't really have anything to do with how stuff works in practice.
How like the software industry that we end up in a binary argument about whether "solitary" or "collective" programming is better. Just because we work with data that is either 0 or 1 doesn't mean that we have to be that way.