[revoltingx]

I spend much less time speaking or writing about PERL than I do writing PERL code.

Note, I'm well aware that PERL is not an acronym. I ALWAYS spell it like that because I like to make it pop in my sentences. Frankly, if an employer is turned away by the way I spell PERL then I don't want to work for them.

My work speaks for itself.

[whiskeyjack]

The thing is, savvy folk know it's Perl and not PERL and regardless of your work, it indicates a lack of knowledge of the community.

[revoltingx]

I really don't communicate with the Perl community at all. I write code, I send bug reports or bug fixes if things are broken. I really don't see how interacting with the Perl community would be relevant to an employer from an engineering point of view.

At that point it's not 'savvy' people who know that, but silly people who have too much time to complain or notice small things like that. Possibly managers or scripters, not engineers who go only by code, architecture, etc.