Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Tuesday September 03, 2002
06:46 PM

You never can tell

[ #7507 ]

Just finished interviewing two programmers. One we thought of as a junior developer and the other seemed to be much more mature in his coding ability. As it turns out, the "junior" turned in a much more mature program for his coding test and, though he had a slight bug, I was pleasantly suprised. The one I thought would be better just threw a bunch of code in a while loop, didn't modularize anything, used 'chop' instead of 'chomp', didn't know how to use Perl's time functions (though he had both Perldoc and Programming Perl available) and generally turned in something that I simply wasn't too impressed with.

The test, incidentally, was basically to display a menu which allowed you to list a log file (in the format of your choice), add a datestamped entry to the log file or exit. Pretty simple stuff that I whipped out in five minutes. Both of them took almost half an hour :(

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

    by samtregar (2699) on 2002.09.04 0:07 (#12473) Homepage Journal
    Are you sure you're testing programming skill and not just test taking ability? I ask because I'm a really good test taker and I know how much that slants the odds. If you sat me down with a programming manual for a language I'd never touched I bet I could beat an average test taker with one year of experience in the language. Would that mean I'd be the better guy for the job? Probably not!

    Also, did you make them write it down on paper? I absolutely hate trying to program in pen. I've been tempted to walk out of interviews when I see them take out the xerox of questions...

    There, I feel much better now. Maybe I should start using my own blog.

    -sam

    • Actually, I think you probably would be better for the job. I'm a good test taker as well, but this is limited to the classic multiple choice tests where the elimination strategy works 80% of the time. The sort of test discussed here is a little different: if you can sit down with a manual of a language never seen and whip out a working and correct program then you can probably pick up everything you need about the language to get your job done. Yeah, you're missing idioms and other features you can reall

      • Well if that's the kind of programmer you want then you might as well test for it explicitely. You could create a manual for a fake computer language, give the applicant an hour or so to read it and then have them do a few test programs. This was actually done in my CS 202 class at college and it was the most fun I've ever had in a test.

        But I'm still really concerned that you'd be missing out on some fantastic programmers that have a different psychology.

        -sam

        • I can almost see your point, but the nature of the questions that we pose to candidates are so basic (e.g.: what's the potential performance impact of nested loops?) that I am very concerned about someone's inability to respond to them. In contrast, in the Perlmonks thread I started on this topic, someone mentioned writing a routine to go through a binary tree without recursion. While this was described as simple, I find that I encounter nested loops far more frequently than binary trees. I could easily

    • Good question. The questions are here [perlmonks.org] and we do ask that they sketch out the answer to the second question. The rest we can just discuss as I want to know how they think, not necessarily whether or not they get the answer right. Now, if I had difficult questions, I think this could be more problematic.

      As for test taking ability, to a certain extent, some of us could argue that this is what all programming is about. The boss runs in screaming "Oh shoot! The knerflebitz aren't fribitgizting! What do w