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.
| [reply] |
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?
| [reply] |
Bring it on disk if you want, but also print the 50 pages of code, prepared to give it to the manager to keep, barring any NDAs or the like. If you can't let him keep some chunk of code, that's fine. He'll understand.
Here's the scenario you want: You whip out the stack of code, with your best stuff on top. Paper clip sections together. Hand him different packets. "Here's a command-line utility that is a grep for image files. I'm really proud of that one because X, and it wound up saving the marketing department 2 hours a day." He thumbs through it, sees that it is well-written code, clean enough to eat off of. Your pride shows. "Here's a module I wrote for tracking ICBMs, using Parse::RecDescent. What's cool about this one is...."
Now, he may go looking at the code if you give it to him on disk. Maybe he'll want to show others in the department. But when you're face-to-face, and you're showin' your stuff, if it's not on paper, chances are he's not gonna see it.
"Show me the code!"
| [reply] |