Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re: What you refuse to see, is your worst trap

by mr_mischief (Monsignor)
on Jun 30, 2003 at 16:20 UTC ( [id://270210] : note . print w/replies, xml ) Need Help??

in reply to What you refuse to see, is your worst trap

The Linux development effort, Extreme Programming, and several other communities have bourne this out without neccessarily taking the same path of discovery. Peer review and letting a code snippet speak for its own quality are known to be good things. This gives us some additional insight into reasons why.

I actually think that there are other reasons why regular peer review of code is good, too. Sometimes, no matter how much ego you get out of the way, starign at the same problem too long just keeps you from finding the source of it. You look somewhere that looks like the source of the problem, build a conception in your head, and can't look anywhere else to find the bug. This particular problem happens even when you didn't write the code. Sometimes a fresh set of eyes is just needed to break you out of a rut.

Christopher E. Stith

Replies are listed 'Best First'.
Re: Re: What you refuse to see, is your worst trap
by chromatic (Archbishop) on Jun 30, 2003 at 17:57 UTC

    Several XP discussions bring up the idea of "egoless programming". Weinberg's well-known in those circles.

    As far as XP goes, though, there's a whole lot more than just regular peer review. Pair programming is recommended for all code that lives longer than a day. The entire team owns the entire codebase; there are no little fiefdoms. Debugging's less important because the code is frighteningly well-tested. The test blindness is lessened, partly because of pair programming but mostly because of test-first development.

    XP's not perfect for everyone in every situation, but it takes into account many of these psychological issues.