in reply to What 'should' a professional PERL programmer know?

I use perl profesionally, but neither my current nor previous jobs related in any way to Perl...
It just happens to be my language of choice that allowed to solve tasks efficiently.

Nowadays I am programming assembler allowing Perl to help me a great lot of deals.

Plus, I am using Perl while on the road - doing my own hobby tasks.

Welcome to the club :)

  • Comment on Re: What 'should' a professional PERL programmer know?

Replies are listed 'Best First'.
Re^2: What 'should' a professional PERL programmer know?
by perloHolic() (Beadle) on Jan 09, 2015 at 14:52 UTC

    Thank you vkon

    I too use perl 'professionaly' and my job is not related to perl either, i use it in much the same way as you, to make quick work of tasks both simple and complex. I do find perl lovely to use, hence why I seek to gain employment in a job geared toward it's use, for personal enjoyment and knowledge growth purposes

    As I replied to choroba's fine comment, this is where i'm failing to understand where the definition lies between me using perl in my current job, and knowing sufficient knwoledge of Perl for an actual career in it.

    Take my current employment for example, I had to take a test in order to get an interview, which looking back asked me to demonstrate the basic knowledge of OO programming, structure, polymorphism and algorithms. This I didn't find too challenging as I had recently graduated from University, and this sort of task was commonplace during my studies. So hypothetically, what would a test be aimed at for a junior Perl programmer would you think? Similar programming fundementals,regardless of language like my current positions test, or things more specific to Perl itself perhaps?

      So hypothetically, what would a test be aimed at for a junior Perl programmer
      I'd say so. Senior roles involve not only deeper understanding of the tools (i.e. Perl), but also the broader view: understanding of the business, leadership skills, etc. Participating in a project with 100+ developers, automatic builds, issue trackers etc. is quite different to writing super clever solutions to HackerRank problems.
      لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

        Another way of saying it might be ... simply to observe that you are coming in more-or-less “from University,” therefore what might correctly be said to be, “entry-level, and how exactly could it be otherwise.”   So, you were asked to take a competency test, which of course you passed.   As you move from job to job and your experience both broadens and deepens, so will the interview processes that you face.   They can check your references, now, because you are beginning to accumulate them.

        And, to further clarify what I’ve said elsewhere:   I have never hired “entry-level” at all.