The amount of work needed to make the module release worthy is also an issue ;)

Just an observation here -- I've found that when working on a module of any significance in the workplace, it pays off to write the module as if you were going to release it to CPAN -- even if you never plan on doing so. By coding with this assumption in mind I am far less likely to cut corners, because there's always a chance that my dirty underwear will be strung out on the line.

And really, whoever ends up maintaining your code will thank you for the extra attention to detail.

Matt

In reply to Re^3: Practical suggestion for accessing configuration data stored in XML format by mojotoad
in thread Practical suggestion for accessing configuration data stored in XML format by fuzzycow

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.