Sanctions for not following a formatting standard, when perltidy can be set up to give you 95% of any reasonable format you desire? That's why it's a nonissue: people can just format the code with perltidy the way they like it as they work on it, then use the company standard perltidy profile when they commit the code to source control.

There are other things that are nonnegotiable: using strictures, using the company source repos, unit tests, code reuse, etc. Doesn't matter how good a coder you are, your practices are part of your output, and if you can't fit into the team, then your boss has to question your continued employment.

In reply to Re^2: Seeking Best Practices - does your company follow a standard? by cleverett
in thread Seeking Best Practices - does your company follow a standard? by meraxes

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.