>That's a damn good point, Whil, and one that can't be overstated. Don't tell 'em what you're doing: If they are reasonably competent they can see that. Tell them why. Good, good point. I would add that for this to work you have to adhere to some sort of rational standard for object and symbol naming.

Careful John, you almost hit another commonly found documentation mistake that annoys me too. Folks who think their code is "self documenting" because they adhere to a consistent & abundantly naming standard (usually the same as VFP docs suggest). It's these folks who are the source of little gems you stumble across like...

*ROX* imagine a screenful of code, 
*ROX* followed by this line with NO comments at all

lcSomeVar = This.oSomeObject.MyObscureMethod('param1ofmany',123120347,.F.,.F.,'anotherparam','andanother','andanother','toodangmanyparam')

*ROX* whole bunch more gyrations here with lcSomeVar

So you walk up the developer (with your shades on of course so that your not blinded by their brilliance < smirk >) and say "Why are you calling this MyObscureMethod here?" and they begin telling what the syntax does and make mention to look at their wonderful naming conventions for more insight.

=D)

I kid you not... I've seen it more times than I care to remember and at different places. In fact the rapidly expanding public domain JavaScript libraries have been infiltrated with this breed of developer. I'm beginning to think it's a conspiracy...

I havent figure out a equivalent punishment like the "Doh!" on the old noggin, but if anybody's got any suggestions? ;)