Yes, this is good. And Roberto, you're right, in my experience if people don't document code as they're writing it, they rarely find time to go back to do it.
I always try to write comments explaining tricky code as I'm writing it, otherwise I myself am likely to forget how it works. For a complex proc like ad_form I didn't write the documentation in the header until I'd had some experience working with it as the design kept changes as I built real-live forms. But I usually document the general functionality of a simpler proc as I'm writing it.
In another thread the subject of writing down coding conventions came up, starting with pre-existing aD stuff as a base.
Conventions for documenting should be part of this.
Jim ... do you need a folder or just commit rights to the relevant portions of the CVS tree?
