Re^4: top ten things every Perl hacker should know

[apotheon]

No, not that again. There's a big difference between saying it's important to know Perl is not PERL if you're going to participate in the Perl community and saying I wouldn't hire someone for not knowing Perl is not PERL. I suspect I'd be less likely to hire someone that called it PERL on a resume, but not because of the capitalization — it's probably the case that the qualities I'd look for in a candidate would match up with the likelihood of knowing that Perl is not an acronym, though.

In other words, I wouldn't mark you down for not knowing it's properly Perl instead of PERL, but I have a sneaking suspicion that calling it PERL is more likely to be accompanied by a lack of qualities I'd like (such as involvement in open source development communities).

In any case, the point of this is that it's something people should know to get along in the Perl community, not an indictment of people who don't know them. Everybody starts out ignorant: knowledge and wisdom come with (not necessarily formal) education and experience.

[DrHyde]

Remember that a lot of CVs that you get from agents will have been mangled beyond all recognition by the agent. That a CV from an agent says PERL doesn't say a thing about the candidate.

That's why, as a candidate, I usually take my own copies of my CV to interviews, to replace the broken one the agent has given them.

[apotheon]

Good point.

As I said, the spelling of PERL on the resume wouldn't in and of itself cause me to pass over a candidate, but your point about recruiters might be an important point to keep in mind.