Don't you also need to qualify the experience level of "someone else". ... Can a professional of average compentence ...

A professional is a professional. A thousand years ago, under the guild system, if someone claimed to be of a specific rank in a guild, you could be reasonably certain that this person could do X, Y, and Z. You (usually) didn't get awarded a given rank without having performed a certain amount of work to demonstrate your skill.

I'm not advocating that Perl go the route of certifications or other such items. But, when I write code to be maintained by other Perl professionals, I expect a strong understanding of certain concepts. Things like recursion, references, safe I/O interaction, and the like. I expect a passing familiarity with others, such as the symbol table.

No, I don't expect that only wizards will maintain my code, but I also don't expect that monkeys will, either. Now, if my employer chooses to employ a monkey to maintain my code after asking me to write Hal (of "I can't let you do that, Dave" fame), that's my employer's problem, not mine.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^4: Commonly accepted style guide? by dragonchild
in thread Commonly accepted style guide? by dragonchild

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.