comment on

Not in favour -- but I didn't downvote your node. :)

Certification doesn't really carry any meaning to me when it's associated with Perl. So someone with a certification knows seven ways to use split. Huh. But can they write good code?

Joel Spolsky, pretty smart guy, has a great article about interviewing, and he posits two requirements for a hire: a) smart, and b) gets things done.

One or the other doesn't do it: if they're smart, that's handy, but of they are 'completion challenged', that's no good. Or if they're really hard workers, but go about their task totally in the wrong way, that's not very productive either.

So my question to you is, what have you taken away from these discussions about Perl certification?

Why do you think it's a good idea, or is necessary?

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Re: Perl Certification by talexb
in thread Perl Certification by cosmicperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks