On Tue, Mar 14, 2000 at 12:11:46PM -0500, Clinton Pierce wrote:
> Elaine -HFB- Ashton wrote:
> > Certificates and certification are not the same thing. [...]
>
> Agreed, and certification is what's needed. Just because they've sat
> through a class, and even if the instructor thinks the programmer is
> good enough to be certified
>
> > If there is to be a certification standards board who grants such things
> > they have to evaluate and give their stamp of approval. The certification
> > is only as good as the granting organisation. [...] ...someone just needs
> > to start doing it as I doubt that there will be any agreement [...]
>
> Well, there's a few things we'd need to know before setting up, even if
> we just hack something out quickly. First, will there be multiple
> levels of certification (Newbie, Competant, Fluent, Abigail) or just a
> single level of certification. Next we'll need to build a list of what
> we consider to be the skills required to be at any of those levels.
My personal vote would be for:
Certified Perl Programmer
knows Perl syntax (typically one 5-day course)
Certified Perl Application Developer
Has passed tests for N (2? 3? 4?) add-on modules of training,
eg: OO Perl, Internet and Web programming, Database programming,
Systems programming, Network programming.
Master Perl Application Developer
Has passed tests for some greater number of the above modules,
perhaps 2N?
That's just what I bashed out when I was chatting with people over the
weekend.
> Finally, a testing procedure will have to be developed, as I know my
> boss isn't willing to accept a certification just because the instructor
> says it's so.
>
> So where do we start?
On the perlcert mailing list :)
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Internet and Open Source Development, Consulting and Training
Level 13, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949 Fax +61 3 9614 0948
