I sympathise with your view but do also remember that the way to improve your skills is to practice them. Also, it is wise at least to do a quick mental code design of both approaches (with or without the module) before committing yourself one way or another. If the module fits the requirement nicely then it is likely to be the right choice. But if it doesn't fit then it is bad design practice to use it for the given purpose and leads eventually to more work having to be done, to try to hack an incorrect solution into shape from the very beginning.

As a rule systems may be designed properly from the beginning but get hacked by changes in requirements over time -- the day comes when there is more hacking than original design and this drastically lengthens the support and maintenance work according to a law of diminishing returns. It is then only a matter of time before a rewrite is needed. Starting out from the beginning that way (by hacking an existing but ill-matching solution such as an ill-fitting CPAN module) dooms your system to a limited lifetime and ultimately (though not immediately) will (quite justifiably) destroy your professional reputation. It may be hard to see that if you don't actually analyse the consequences of your decisions and instead remain oblivious to their impact going forward. I have also seen people with more than ten years should-be relevant experience who still can't code because they got into such bad habits early on.

-M

Free your mind

In reply to Re^3: File::Temp randomness when forking by Moron
in thread File::Temp randomness when forking by ryantate

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.