>Basically, my view is that highly cohesive code tends to be shorter and often doesn't need one comment to describe it if the name is descriptive. Sometimes listing the incoming parameters can be helpful.
>>>
I agree. One exception is convoluted decision expressions e.g.
(!A OR (A AND B)) AND DAY(tnDate)=3
I think that one makes less errors if one comments it heavily. You can do it both before coding or after coding: if I look at a one of these logical expressions and I can't make heads or tails of it I go back and find away to both simplify it (if possible) and explain it. It's cause I pity the poor...

I also wish that the documentation could be linked to the source code so that they could be at the finger tips of the developer or maintainer. Wouldn't it be nice to be able to go to the class hierarchies, object hierarchies and relevant database documentation from the program editor (Modi Comm)? That doesn't sound so complicated...