Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Questions (Score:3, Interesting)

    For the last two hires I had, I threw together a few questions about Perl to smoke out anyone who obviously had never done anything with the language.

    What are the differences between C<our>, C<my> and C<local>?

    What is C<$!>?

    What is C<$_>?

    What is C<$&>?

    What is C<$1>?

    How do you delete a file?

    What does C<TMTOWTDI> mean?

    How do you implement a list of hashes?

    I figure that someone who's been using Perl for a while will know all these. I don't like memo



    • Re:Questions (Score:3, Interesting)

      FWIW, I would not expect everyone to know what our() or $& is; the former is new, the latter is rarely used. I would not care if anyone knew what TMTOWTDI is. Of course, that they cannot answer the question accurately isn't a bad sign, necessarily.
      • Re:Questions (Score:2, Interesting)

        Right, none of them are necessarily exclusionary. It's just to get a feel for what the person knows overall. None of them are make-or-break. (Well, maybe $_ is)

        I make a big point of starting out the interview by saying "You will not know the answer to everything I ask. You will not have experience in everything I ask about. Please don't think that any one question is going to kick you out the door."

        It's not just Perl stuff that I make that comment for. For instance, I was looking over some sysadmin part of this guy's resume, and I said "Hey, have you done anything with LDAP?" He about fell over trying to look good while saying "No." LDAP isn't a requirement, I was just interested...