I agree with the OP: The (most reasonable) design process consists of first identifying the functional (i.e. language-independent) algorithm that solves the problem in the theoretically most appropriate way.

After that, modules may well exist to fill in some of the coding requirements, but it is often wrong to use a module which misses the mark even slightly. For example, if a module can do everything with a set a files except just one of the things you need, it might be hard to justify doubling the number of passes through all the files just to use the module for most of the requirements, especially if there are hundreds of files adding up to several gigabytes of data to be processed.

One world, one people

In reply to Re: On modules by anonymized user 468275
in thread On modules by samizdat

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.