Hi Dan, As usual, I know that when I see your name in a thread here, there will be a thoughtful, clearly written and useful response. But my tongue was firmly planted in my cheek.
Did you happen to take a look at the link to the cartoon Malcolm posted? :) -- rk -----Original Message----- From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dan Covill Sent: Wednesday, September 28, 2011 1:11 PM To: profoxt...@leafe.com Subject: Re: [NF] Measuring code quality On 09/28/11 06:45, Richard Kaye wrote: > Code review? WTF is a code review? Assuming you're serious, a code review in it's simplest form is just having a colleague look at your code. Big companies make an art form of it, with formal meetings etc., but the basis is that a second pair of eyes is a great way to spot problems. I think it's even better if you discuss your code organization and strategy with someone else BEFORE you've got it done - easier to change and there's less emotional investment. We always say, "The best way to find a bug is to explain to someone else why the code is correct. If you can't find a co-worker, then explain it to the dog. That works, too." Dan Covill _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04419F491F4BC@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
