But I don't have such code. I've been programming for years, and there's no singular piece of a couple of lines that stands out. It's mostly boring, readable, well designed code that is maintainable. There's nothing sexy about that.
Sure, I'm proud of some large pieces of code. Thousands of lines that span an MVC architecture and three different platforms, for example. But the interviewer can't possible take the time to read it all and understand why I'm proud of it.
Should I whip up something incredibly complex, using the most esoteric syntax elements possible for optimal premature optimization, a nightmare to maintain, just to appease interviewers in this situation? What do you do HN?
[1]: http://en.wikipedia.org/wiki/Fast_inverse_square_root#Overview_of_the_code