... if those 4 techniques are implemented in standard/best practices. For example, if you hired a developer and he wrote code like the examples I provided, would you find it acceptable?

Those are two different things, which is kind of what the earlier post was getting at. For example, I'd say copying/moving/deleting files via system is almost certainly not a best practice (the File::* modules are in the Perl core and therefore almost always available). Is it "acceptable"? Sometimes, if the appropriate care is taken and the strings being interpolated into the command are well-known. If it's fairly easy for you to find a test case that shows a failure, then it's a problem!

In reply to Re^2: Advice on best practices by Anonymous Monk
in thread Advice on best practices by goldcougar

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.