in reply to Re^2: perl certification
in thread perl certification

Because, as eyepopslikeamosquito pointed out, so many of those who hold certifications are not good at what they are certified for.

Certifications are only a positive if the guy/gal holding it can demonstrate good working knowledge on and beyond the subject of the certification. But if they can do that, they shouldn't need the certification in the first place.


Replies are listed 'Best First'.
Re^4: perl certification
by Anonymous Monk on Jan 24, 2014 at 16:07 UTC
    Even if the guy that has the cert can't fully apply what he has learned, he still has gotten his feet wet in the language. So, to me this shows initiative. Everyone is so hung on experience. I'm guessing you guys haven't worked with the guy that has so much experience, but is just stuck in his not so great ways. In this situation I would rather mold the newbie vs getting the experienced guy who really isn't interested in hearing what you have to teach them. I still say any cert can't be a negative thing. I personally don't have any certs but know guys who do. Some of these certs are not easy to get. You don't just pay money and get the cert. Like I said before, if my choices are two guys with same degree, but one has a cert or two, I definitely wouldn't look down or negatively at the guy who obtained the certs.
Re^4: perl certification
by Anonymous Monk on Jul 23, 2013 at 12:27 UTC
    I understand that they shouldn't need the certification if they have a good understanding of the language. My point is, how can a cert be viewed as a bad thing for someone with the knowledge to back it up? To me, it shows motivation and that the guy spent time doing something that others might not want to do. Why get a college degree if I already have equivalent experience in whatever field? Wouldn't that be the same concept? This thread is about to get entertaining:) -Scott
      What we're saying is that for potential employers who don't just take the short cut of "oooh, certification = good", which we believe is bad practice, and we're arguing that a certification, to us, is a potential red flag; and before an interview you should find the people needed to probe into whether they actually have the technical chops to back that certification; but you should already have those people in the interview whether or not the applicant has a certification.

      If they have the cert, and the tech chops, great, most people will add merit points to the person with the cert over the one without the cert.

      I think it can be boiled down to this: as an employer you should be at least as suspicious of those bearing certifications as anyone else you interview; it should not be an "E-Z pass" into the company.