Well put it this way. If humans read a different document
from the computer, you have a problem. The fact that there
are programmers who do not understand how to code well is
their problem. If you rely on such programmers and have put no
thought into communicating your requirement that the code
have decent quality, then their problem has become yours.
Bad programmers are a hazard to your code-base. So give
them feedback and review. Doing that up front saves energy
in the end over letting it pass and cleaning up after. A
stitch in time and all that.
BTW I do comment most subroutines. Input arguments, brief
description, and return. Often only the ones that are
meant to be used outside the module though...
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.