Because I didn't RTFM, because I reinvented the wheel, because I used a bunch of shoddy workarounds, because yes that is a magic number, because that comment made sense ten versions ago but now it's just confusing gibberish and I'm to lazy to update it, because I didn't properly use Google or PM Super Search, because I didn't indent properly, because I used "or/and" instead of "||/&&", because I told myself "I'll clean that up later", because I didn't properly listen and understand what the other monks told me, because I decided to do it quickly instead of correctly, and because I stubbornly refused to learn how to use the module that would just do that correctly for me every time in favor of doing the code equivalent of insisting on screwing together IKEA furniture using a coin from my pocket just so I don't have to walk 10 feet to the closet to get a screwdriver...
...Oh, yes, and because I'm an idiot. :-)
Just another Perl hooker - My clients appreciate that I keep my code clean but my comments dirty.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
