The sections at PerlMonks are mostly not by topic but by intent. So, if you want to share (and discuss) a best practice that you discovered, then you post to Meditations. If you want to seek Perl knowledge about best practices of some (hopefully specific) type, then you post to SoPW. If you want to provide a detailed, gentle, and polished presentation covering best practices, then you might post to Tutorials (after getting some feedback, such as by posting a draft to Meditations).

If you want to find a bunch of discussions about best practices, then things get a bit more complicated with a lot of possible approaches, none of which is perfect. But adding a dedicated section in hopes of addressing that is not a more perfect solution, despite it sounding simple and effective at first blush. Most threads cover more than one topic and so attempting to partition up threads into groups based on subject is fundamentally flawed. Once one realizes this, one next jumps to building overlapping groups of threads by topic. And this is a fine approach but the devil is in the details. And most of the existing approaches do just that, choosing different ways of determining who gets to pick which threads are appropriate for inclusion under which topics.

And a big problem to solve is motivation. You are currently motivated to collect information about best practices. So I suggest you Super Search and google and such for threads on that topic and for existing collections of links to items on that subject and start building your own collection. You can start building this collection on your home node or your scratchpad. As you notice gaps or other issues, you might be inspired to seek wisdom within a specific gap or to try to fill a gap or improve upon existing information sources. And to do that you might consult my first paragraph again. (:

- tye        

In reply to Re: RFC: "Best Practices" code review section (orthogonal) by tye
in thread RFC: "Best Practices" code review section by rvosa

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, 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
  • 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.