>HI All,
>
>This has been a pet-peeve of mine for some time. A long long time ago, when disk space was sparse, comments in code was frowned on. Too many comments would bring sever finger shaking at me. "We can not afford wasting disk space!" OK. That was then, this is now, with terabytes of disk space, why not take the time and place a comments as to what the code is intended to do? I still see new code with very little to no comments to help me follow the purpose of the code. Not to mention (ok, i will), planning the flow of the code ahead of coding.
>
>Why is this? Should I be striping the comments out before sharing it with others, and to help confuse myself years later when I revisit the code for maintenance?
>
>Only looking for comments on the subject. ;)

My policy is that any time I have to stop and think about what code to write next, it's time to comment. Also, anything odd or non-standard. (Found a code yesterday in a MySQL SP saying that the way I had written something seemed ugly, but I couldn't come up with another approach. That's an invitation to find a new way.) Also, any changes with dates, so we can trace issues that arise.

Tamar