On Jun 4, 2006, at 2:02 PM, Andrew Lentvorski wrote:
When there are lots of hands touching code, this just isn't feasible. The code has to speak for itself.
The problem with this is that I see no reason for lots of hands to be working on one segment of code at one time. How man people, really, need to be working on the same function/method in a source file at the same time? And if there really are three people working on the same method, you've got worse problems than just making sure the comments associated with the code are sensical.
In the limited environments I've had opportunity to work on so far, managerial methods were in place to avoid having multiple people working on the same thing at the same time, which I suppose has spoiled me. :)
No argument. A friend of mine calls it "psychic commenting"; whenever he hits a clever section he invariably sees a comment right there. I'm very good about being straightforward. When I am not, there is a comment. Generally with a hyperlink to the external reference, as well.
I see we are in violent agreement. :) Gregory -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
PGP.sig
Description: This is a digitally signed message part
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
