I was not aware that so much discussion about Perl certification had already taken place (though it makes sense that is has). It DOES sound like quite a tough pickle. But you have to imagine, if any group of people were to be able to find a way to make a proper certification program, wouldn't it be a PerlMonger group? Though, I do see what you're saying Uri. You can't really look at Perl coding (or other coding) as simply... well... coding. There's a mentality and thought process to make coding be "good" coding. This DOES make making a good certification program rather difficult.
Still, it makes you wonder if it would be possible... --Alex >>>>>> "AB" == Alex Brelsfoard <[EMAIL PROTECTED]> writes: > > AB> I like this idea. I think Perl certification WOULD make the world > happier. > AB> Then again, I like Greg's idea. > AB> Think maybe some of us PerlMongers could get together and actually > start > AB> up a real Perl certification program? > > oy!! > > perl cert has been argued at length in many fora with no victor. my > sense is the majority don't want it since it will be only used by those > who don't know perl :) > > ever find an MSCE who actually knew something? most certified computer > people just pass a test but don't really know the subject. and mangler > who hire based on required certs just don't get it and they get what > they deserve. > > setting up a cert group is a major project. note that most certs are > sponsored by the corp behind the product and perl doesn't have a > corp. or they are crapola ones like brainbench. perl is also too broad > and deep to properly create a standardized test. does it cover OO, CGI, > CPAN, regexes, data structures, etc and how deep? specific modules (i > have seen that and it is very dumb. you can always read the docs if you > don't know a module)? > > i judge a perl (or any coder) by how they think, interact with problems, > how they solved problems in the past, etc. this is best done with a > general interview and getting them to talk about their past > projects. see the depth of their knowledge in their project areas. see > if they have the big picture and attention to detail. see how they use > their experience and skills to solve the project problems. see how fast > they pick up on project info you give them. > > those are all untestable skills and they are much more important than > any rote test. if they have those skills, they can learn what is needed > on the job. if all they can do is parrot book learning, then you will > get a parrot. > > uri > > -- > Uri Guttman ------ [EMAIL PROTECTED] -------- > http://www.stemsystems.com > --Perl Consulting, Stem Development, Systems Architecture, Design and > Coding- > Search or Offer Perl Jobs ---------------------------- > http://jobs.perl.org > _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
