One disagreement.

Copious documentation in my experience tends to become bad documentation. Documenting everything leads to unmaintained comments that, over time, wise maintainers learn to ignore. Documentation needs to have a clear purpose, accomplish that purpose, and not attempt to do more.

As I0 said a long time ago, I find the most useful comments state what remains invariant, while the code states what gets transformed.

A past thread on this is Re (tilly) 2 (disagree): Another commenting question,. A couple posts into that thread you'll find a set of coding guidelines for when I do (and don't) comment, and why. I still pretty much follow that.

In reply to Re^2: Nice clothes (Term::ProgressBar, perltidy, Getopt::Declare) by tilly
in thread Nice clothes (Term::ProgressBar, perltidy, Getopt::Declare) by water

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.