I'm a little bit on the fence about what to tell you, since I've made good money as a consultant fixing other people's broken Perl code. What was broken about it? It was impossible to change or debug because it was written in the quick-hack style you are describing. Eventually, some managers would get fed up with the difficulty they were having making changes or fixing problems. Then they either hire someone like me to fix it, or declare that everything is going to Java.

There's the rub: you know how people who don't like Perl are always bitching about how they can't read it? This is why. And the more people write crappy Perl code, the more it reinforces the notion that Perl is only good for writing crappy code.

Why do we recommend solutions involving strict, templates, tests, etc. to people on Perlmonks? Because we tried them, and they worked really well. Becausse unlike my consulting gigs, no one pays me to answer questions on Perlmonks, and I get tired of helping people with something that would have been instantly obvious if they had used strict.

On the whole, I think that reminding people of what has been shown to work is a positive thing. I might choose to extract data from HTML with a regex, but it doesn't hurt anything for me to know that many people think a parser is the best way to do it. It might even help.

In reply to Re: Perlmonk's "best pratices" in the real world by perrin
in thread Perlmonk's "best pratices" in the real world by schweini

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.