You misunderstand why I have that rule. If you have code on CPAN, that means I can read it. If you are vouched by someone who has code on CPAN, I can see the quality of the person doing the vouching. That gives me a standard by which to measure the work you will do on MY code. Yes, you're right - there's a lot of dreck on CPAN. That means I know not to hire that person.

Some background - I was a consultant for several years and in every interview I went to (often 2-3 every 6 months), I'd be asked for code samples. Well, I didn't have any because everything was owned by the employer. CPAN, for me, was a way of getting code that was mine that I could show a prospective employer. And, more importantly, it showcased my abilities to provide independent value, manage large projects, and work with clients.

Anyone I hire is going to fall into one of two categories - experienced or intern. If you're experienced, I want to see proof of that. In Perl, that probably is going to be CPAN. If you're junior, I'm hiring you cause I know your professor at school through another set of networking.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^4: Perl Certification revisited by dragonchild
in thread Perl Certification revisited by cosmicperl

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.