One thing I am a fan of is reading over my changes at the end of a session and
updating to-do lists, especially when it reminds me clean up my comments and
rewrite quick-fixes to proper code the next day ;-)
It's generally my opinion that the comments tell you what it does and the code
how (with comments for the less obvious). If the comments fall out of sync
with the code, the comments should be updated once the code is less likely to
change to much. Personally I think documentation about using the program
should be separate from the regular source code. Documentation about working
on the program and it's sources should be kept near by. Just how much, is a
matter of developers tastes.
I advocate people using common sense, that is to us the gray matter
approximately three feet above their romp roast.
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.yqcomputer.com/