Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re: Re: How to measure Perl skills?

by Vautrin (Hermit)
on Mar 23, 2004 at 01:04 UTC ( #338859=note: print w/ replies, xml ) Need Help??


in reply to Re: How to measure Perl skills?
in thread How to measure Perl skills?

I agree. The only way you can clearly establish a coders credentials in a short amount of time is to look at their portfolio. See what work they've done in the past, if it's up to snuff, and have them explain what they did and why. (People might not use strict; for a reason -- i.e. they inherited a code base like yours. Best if they explain themselves and you don't jump to conclusions -- you might pass over a great coder!).


Want to support the EFF and FSF by buying cool stuff? Click here.


Comment on Re: Re: How to measure Perl skills?
Download Code
Re: Re: Re: How to measure Perl skills?
by flyingmoose (Priest) on Mar 23, 2004 at 13:56 UTC
    This isn't exactly fair if they have mostly commercial work that they cannot share. I know this is true of me -- I want to code in my spare time, but 50 hrs a week of staring at a monitor is usually enough for me.

    I think the best is to measure analytical skills, ask them to walk you through a previous design, or so on .. or maybe ask them to explain one of your Perl programs.

    But don't get TOO technical. I had a few interviews from PhD types who thought they were Gods gift to computer science (giving a bunch of problems they thought were clever, but really weren't -- and then made up arbitrary restrictions to limit my ability to solve them through 'normal' means). They rubbed me the wrong way, were full of themselves, and I wouldn't have wanted to work for those sort of elistists.

    So it comes down to ... (1) can they work and play nice with others, and (2) can they think on their feat and do they have a general grasp on good design, and (3) I think it's perfectly fine to ask if they understand closures and lexicals. You see, this is what distinguishes a basic hack-and-slash 'scripter' from someone who is into the stuff from a programming perspective. Maybe. Just don't become that PhD jerk who thinks he is smarter than the interviewee. Intimidation does nothing for anyone, and will problably just make your subject feel uncomfortable.

      If a person is going to experience intimidation and pressure in the job itself, then perhaps it is useful to see how applicants deal with it during the interview.

        Perhaps this is true, but I have never seen a more cocky and arrogant interviewer in this case. My post did not reflect that clearly. He was clearly trying to justify his credentials and rank, tooting his own horn, etc. When I am on an interview, they are interviewing me, but I am also interviewing them -- these are the people you are going to work for, after all, and it goes both ways. If *they* have problems working with others, it's just as bad if someone else does. Similarly, if they don't know their stuff, and they are team lead -- you should be very afraid -- but you have to be subtle, and learn this by observation and by basic questions -- you can't get aggressive like they are allowed to be, as you are the interviewee.

        Don't just land a job at all costs -- you want to want the job too. Else you'll just be unhappy. No amount of money makes unhappy worth it, which is a lesson we all eventually learn the hard way.

      I realize that it's not always possible to view a coders best work -- even if you have the option of signing an NDA (which you don't always). However, I think that it's the best way to evaluate a coder if you can see examples of their previous work.

      Want to support the EFF and FSF by buying cool stuff? Click here.
      My attitude is the diametric opposite.

      Code samples need not be long to be useful. Any competent person should be able to sit down and in a couple of hours have a code sample that gives an idea what their coding level is. If you can't produce code on demand before you're hired, then why should anyone believe that you will be able to after you're hired?

      Of course anyone who codes in their spare time will have code available on a moment's notice. But even if you don't, asking for you to produce a code sample is not an unreasonable imposition.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://338859]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (6)
As of 2014-12-28 03:16 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (178 votes), past polls