To expand on
lhoward's points, consider some of the basics in developing a large project:
- Specifications
- Design
- Implementation
- Debugging
- QA
Presumably, the specifications are already done, or else you wouldn't necessarily be at the stage of choosing modules. The other issues, however, can be broken out on a very detailed level ... and should be. Proper work up front guarantees a lower TCO. Since many Perl modules are huge, you even find that the one module function you want is not cost-effective. If that's the case, you should be fair and not insist upon using it.
If you like this post, vote up lhoward's post instead. He's the stimulus behind this.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just go the the link and check out our stats.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.