in reply to Proving I have mad perl skillzzzlz

I can't recommend Nick Corcodilos' book Ask The Headhunter highly enough. (He also has a website http://asktheheadhunter.com) It will help shape your thinking about the interview process. That you phrase it as "prove to my employer" rather than "get my employer to see" is a huge step. Nick says that you prove it by doing the work for the employer in a sample situation. Get a real problem that the employer actually has, and solve it in front of the boss.

As an employer myself, I put a lot of weight on the code samples that I'm shown. I can tell a lot about someone's work habits from their code. I don't care if you're a vi or emacs user, or if you prefer 4 or 8 tabs, but I do want it clear that you care about your code.

xoxo,
Andy

Replies are listed 'Best First'.
Re: Re: Proving I have mad perl skillzzzlz
by BUU (Prior) on Dec 23, 2003 at 04:01 UTC
    That book you reccomend looks interesting, I'll have to read it. As for the code samples, those sound somewhat like what I was thinking about, could you perhaps elaborate on what type of code samples you are talking about or looking for? Like, 4 line subroutines, or large programs or..?
      Ask the hiring manager when you set up the interview. "I'd like to bring in some sample code to give you an idea of the sorts of projects I've worked on in the past, and to show the care I put into my work. What sorts of projects would are you interested in? For example, I've done X, Y and Z."

      If you can't talk to the hiring manager, or he/she says "Oh, whatever," then bring in some of everything. Bring in modules. Bring in command-line utilities. Bring in three-tier web apps.

      Most of all, bring in what reflects best on you, and what you're most proud of. It will come through when you talk to the manager.

      xoxo,
      Andy

        Modules / utilities I'm with, but how should I bring in a "three tier web app"? Print 50 pages of code? Bring it on a disk or something?