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

• Save time (even if you end up only using half of the existing module).
• Learn from other people's code (because you have to understand their module first.)
• Learn to be a collaborating hacker instead of a Lone-Ranger-Coder.
• Get what you want, and in your style (at least partly, in those lines that you code).
• Have less "fame", because the module is not published under your name. So what.

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;
[download]