So you find that the existing modules don't do things the way you want it. Is starting from scratch really the only way to go? I beg to differ. Often, you'll find that a module is close to what you want, even though it is not your style. Why not make some changes so it fits your purpose and submit the changes to the author? This way, you will be able to

True, there are opportunities when you need to reinvent the wheel. Linus decided he needs another OS -- but he was clever enough to make use of the GNU utilities instead of doing everything himself. Linux, emacs, perl, apache -- all these are good examples. On the other hand, there are for example (too) many modules for command-line parameter processing on CPAN. Probably not all of them are necessary...

If you feel you can really learn something valuable from writing the code from scratch instead of just understanding other people's code -- go for it. Just don't expect that everybody else will be enthusiastic about it. If your approach is radically different and helpful -- go for it. If not, consider improving your skills by trying something new. Try to be more lazy and don't do things you don't have to do.

I guess at the end of the day, it all boils down to

use wisdom;

In reply to The Third Way by crenz
in thread Use modules or roll your own? by kvale

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.