begin quoting Andrew Lentvorski as of Sat, Dec 09, 2006 at 10:30:28AM -0800: > Stewart Stremler wrote: > > >And you're right, it doesn't _find_ more bugs -- but if you have > >compatible programmers, it *prevents* bugs. Mostly due to greater > >adherence to discipline (like writing good comments, writing unit tests, > >choosing good variable/function names, etc.), I think. > > The evidence suggests that the bug rate is the same. Hm. Personal experience suggests otherwise -- perhaps on average, across all developers, indicates that non-compatible programmers generate more bugs together than alone. I could buy into that.
> Now, there may be benefit to sharing knowledge about style discipline. It may be that pair-programming works best for this sort of knowledge transfer, and should be restricted to that, rather than adopted as an all-the-time approach. Mostly, in the past (non-XP projects), I've seen (and participated in) pair programming used to tackle difficult or tricky problems. There are people with whom I can program, and the whole is greater than the sum of the parts -- together, more code, with fewer bugs, can be written in less time. And then there's the over-the-shoulder credit.... > However, I have found that design reviews and having to fix existing > code are generally good enough for that. I'm in a process-oriented shop at the moment that has design and code reviews, and they aren't working (well, they are, we're catching problems, but the problems that are being caught are long after the point where it is easy to fix said problems). There's so much process that there's hardly any time left to write code... -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
