I won't comment as to the validity of certification, but free certification? What's to stop me from taking the test a 100 times till I get %100? In the real world (with like Java for example), certification costs like ~$150, so people don't endup taking the test 100 times. The only way I could see a perl certification scheme is if it wasn't free, which brings up a whole bunch of other issues (who's gonna run it, who can give out certificates .... )

Now, as for the "a list of what the programer need to know" you have there, are you nuts?

None of that seems reasonable. Up until recently, java programmer certification required knowledge of AWT (GUI toolkit basically), and now they took it out. Why? Cause It has nothing to do with being a java programmer.

What a perl programmer should know the basics of syntaxt (pod included), datatypes, context, and a generous knowledge of built-in functions.

Now, should a perl programmer should also know the basics of fork-ing? What about platform caveats?
How about threading?
What kind of threading?
Should there be a perl5.6 certified perl programmer?
A perl 5.7 certified perl programmer?

Man that's just too much confusion for my taste.
Since there is no ISO/ANSI perl standard, I feel perl certification would be premature.

Wait, maybe a feature knowledge type of certification is in order?
You go in, you pay your XX amont of dollars, you're greeted by a perl guru (or higher -- 7 stages of a perl programmer) and he asses your knowledge of perl, and you get a certificate looking something like 

John Doe ....
Throrough knowledge:
    forking concepts
    threading concepts
    oo perl
    tie interface
    socket programming
    XS
    ...
I say merlyn,Dominus and TheDamian and others who teach/taught perl for a living give it some serious thought (who's better qualified at designing tests/certification but teachers? not me).

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: Perl Certified! by PodMaster
in thread Perl Certified! by gmpassos

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.