What's wrong with bringing code to a programming job interview?
I'm baffled by the responses to another question that say you shouldn't bring a code portfolio to a programming job interview.
Why the heck not ? Others recommend this; it's even one of the "classic" stories in Peopleware:
“It would be ludicrous to think of hiring a juggler without first seeing him perform. That’s just common sense. Yet when you set out to hire an engineer or a designer or a programmer or a group manager, the rules of common sense are often suspended. You don’t ask to see a design or a program or anything. In fact, the interview is just talk.”
So, what gives ? Any "war stories" of what went wrong when you showed up with a code portfolio ? Or of when you interviewed a candidate who had one ?
Answer
I've done a lot of interviewing over the years, but I've never asked for, or been show, any code. It is not what I'm looking for. First off, I'm trying to establish whether you can work in a team cooperatively. I'm also keen to see if you understand how to deal with all those compromises that employment implies. For a developer, I'm looking to see the way that you approach problems, and your stubbornness to persevere after setbacks.
Obviously, I'll want to get a feel for your level of understanding of the art of programming. If you profess a particular skill, i'll ask you a few technical questions.
I'd never want to see the code you've written. How could I be certain that it is yours, unaided? How could I give it, in the interview time, enough time to inspect and appreciate the finer points? How would I know the time it took you to write?
There is a world of difference between writing a program in tranquility, and the skill of working in a team, under pressure, having to make compromises, cooperate, and make decisions on where to focus your resources.