Personally I tend to (re)invent lots of wheels, but I also tend to throw away my invention when I do find a good module. The problem for me is that finding the correct module and making sure it does what I want is often a more daunting task than writing my own, especially at the beginning of the project when I don't even know what I really will need. I'm a fan of the Agile methodology, which usually means that at the beginning I only need something really simple to get the first working version. As I gradually understand the complexity of the problem, and thus the requirements, I can better judge whether a module will do what I need. At that time, I won't hesitate in using a good module.
So I'd say, invent and re-invent as you see fit, but be on a constant lookout for existing modules that actually do what you want. There are lots of smart people out there.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||