I'm actually a pretty strong supporter of keeping the style of the code you've been given. We've got old code and new code. Injecting new style into old code makes it harder to read and I think it's better to conform on that front. There are limits of course. There is simply too much old code with not enough tests to warrant running over the old style. Too easy to introduce bugs with large scale changes. That code gets the kid gloves treatment until we can define WHAT it does so we can fix it.

A standard I can point to at work that's been gone over and thought about is really something I hope we can get to.

--
meraxes

In reply to Re^2: Seeking Best Practices - does your company follow a standard? by meraxes
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.