Well my opinions on comments seem to be an extreme around here. But read the entire thread starting at Re (tilly) 2 (disagree): Another commenting question, (and keep in mind that behind the scenes we were exchanging much more pleasant /msgs) to see my personal style laid out.

In there I lay out in quite a bit of detail my opinions on ways in which commenting can be negative, what needs comments, what does not, and how to comment. As you will see reading that, the question isn't really the density of comments. It is instead what do you comment, why do you comment, how do you comment, and in what ways do you make your code descriptive?

In reply to Re (tilly) 1: Too much documentation? by tilly
in thread Too much documentation? by melguin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.