I'm becoming convinced that comments in code are close to
useless. The first and greatest problem with comments is that
they don't alter the code's behaviour. When your code's wrong,
you can tell from its (wrong) behaviour. But when your
comments are wrong, you can only tell by comparing them to the
code. And if you're parsing the code to test the comments,
then the comments are basically worthless: you're having to
read the code as though they aren't there anyway.
Even a stale comment tells you something about the code --
you know immediately that someone made a change from the original version there, and they did it very quickly, without thinking it through (or else the comment would've been fixed, also).
If you want to talk about code maintenance, revising comments
(and documentation) is part of the job.
And I'm sorry if this sounds rude, but it's based on experience:
You really don't want to work with people who think their
fabulous code is so beautiful it doesn't need comments
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||