But see, I consder Perl modules
to be extensions of the language environment itself.
Fine. I agree with you.
But guess what?
The manager who objects probably
doesn't,
or s/he'd allow you to use the module, yes?
You'll be more persuasive
if you set aside your own viewpoint for a moment
and try to address the manager's concerns
in ways that make sense to the manager.
For (too) many organizations,
it doesn't matter that Perl's licensing
is flexible and that modules are easy to install.
Using modules save programmers lots of time,
but represent additional work for
someone,
and that costs $$$.
Your argument will be more effective if you take the time
to find out (or estimate) that cost
and then show how much more money is saved
by using the module anyway (a cost-benefit analysis).
Trying to argue
that the manager is looking at it "incorrectly,"
or that there aren't any associated costs,
is just more likely to make him/her stop listening.
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.