I myself have been guilty in my first few weeks of Perl of doing stuff like:
if (condition) {} else { &actually_do_something() }
I did figure out I ought to have done !condition the next day, though it also took me about a year to start getting comfortable with more idiomatic ways to express this:
&actually_do_something unless condition;
Most of us have code from very early on in our learning cycles to qualify as pretty funny if not horrible. I'm pretty sure some of my code fitting these categories is still used in production settings, as well...

I shudder to think what more experienced Perl developers think/say when they come across it. It embarrasses me.


In reply to RE: The inheritance of Cruft by Fastolfe
in thread The inheritance of Cruft by kilinrax

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.