JCWren raises some seriously good points in his post, and has given me a money-making idea that I offer free to the community... why not form a commercial Perl module certification service?

CPAN testers do what they can to make sure that a module passes its own tests on different platforms, but there's little checking on what those tests are all about. Not a criticism-- people have jobs to do.

So here's an opportunity for someone to make some extra cash. Start a company that verifies and supports Perl modules for a price. If you discover bugs, fix 'em and give the author your changes, and the whole community benefits. Paranoid bosses can feel better with some corporate support they're paying for.

On the other hand, I've worked for some fairly large companies-- HP and 3Com-- and the divisions that I worked for had no problem with the use of CPAN modules, so long as I was willing to vouch for them and fix any problems myself. (Thank god I rarely had to do that...) If one explains this to one's boss, one's boss might get entranced with the wish to play like the big kids play. (On the other hand, "because this guy on perlmonks said this is what they do" is unlikely to carry much weight, but hey...)

stephen

In reply to RE: (jcwren) RE: (2) Getting managers to accept Perl modules by stephen
in thread Getting managers to accept Perl modules by Fastolfe

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.