> *always* take issue with the concept of "commenting as you
> write it"! IMHO, it is an order of magnitude more useful to
> comment it *after* it has been debugged and Proven

This is very useful both at the time of completion (for one's
own satisfaction that there are no loose ends) and for
future reference. In 6 months time, code with no or just
general commenting has to be thought through all over
again just to get up to speed reminding yourself why it
was written that way

> I've seen many times that the comments (describing the
> INTENT of the programmer) simply obfuscate the actual
> problem manifested in the CODE

When you're carried away in the moment, fuzzy thinking that
ends up in the code will also appear in any specific comments
written at the time. The error of assuming that such commented
code "works" and doesn't need reviewing can lead to much
frustration and fruitless debugging time. As code errors can,
and often do, appear in the last place you'd think to look, it's
sensible practice to periodically take a break from making
new code and examine and justify every instruction (and
comment) of what's already been done. It may seem a waste
of time but reviewing your own work is perilous at the best of
times and you really need to focus

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads