Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
I find it interesting that so few of these points are Perl-specific.
It's interesting you mention that. The original set of ten I had planned to use were much more Perl-centric (so much so that we wouldn't have called them "Essential Development Practices", but rather "Essential Perl Coding Practices"):
  1. Always use strict and use warnings.
  2. Use grammatical templates when forming identifiers.
  3. Use lexical variables, not package variables.
  4. Label every loop that is exited explicitly, and every next, last, or redo.
  5. Don't use bareword filehandles; use indirect filehandles.
  6. In a subroutine, always unpack @_ first, using a hash of named arguments if there are more than three parameters.
  7. Always return via an explicit return.
  8. Always use the /x ,/m , and /s flags, and the \A and \z anchors.
  9. Use capturing parentheses in regexes only when deliberately capturing, then give the captured substrings proper names.
  10. Never make variables part of a module's interface.

But as I started extracting these guidelines from the book, I realized that they relied on the reader understanding and accepting other, earlier guidelines, which in turn relied on other guidelines, etc. etc. The book is deliberately put together that way, so that the recommendations work harmoniously together and form a coherent approach to Perl programming. Unfortunately that made it hard to isolate just ten of the Perl-specific guidelines and still have them make sense.

That said, if you want to get a better sense of the (great majority of) Perl-specific advice in the book, take a look at the beta chapter we have online.

Things like "write tests first", "use revision control", and "no premature optimization" are almost universal recommendations...
...that people universally don't follow. Hence we thought these ten, though not especially Perlish, would still be a valuable reminder. ;-)

In reply to Re^2: Perl Best Practices by TheDamian
in thread Perl Best Practices by Anonymous Monk

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (12)
    As of 2014-08-22 08:01 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The best computer themed movie is:











      Results (150 votes), past polls