When I used to train developers, I spent quite a bit of time on our standard practices. The argument that I finally settled on was paraphrased from a mentor of mine.

There are an infinite number of "solutions" to any programming problem. Most of them are wrong. Of the remainder, there are still a huge number (probably infinite) number of "right" answers. The purpose of the rules is to reduce the number of minor, useless variations in the solutions, so you can focus on the good solutions.

(Or, something to that effect. I don't think I've taught that class in about a decade.)

In most of the problems I have had to solve, any given set of best practices would not have altered the important part of the solution.

G. Wade

In reply to Re: Best practices, revisited by gwadej
in thread Best practices, revisited by ELISHEVA

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.