> The best candidate I have ever interviewed [...] came to the interview with examples of his code and explained what his code does and why he did it this way. Everybody loved that. Unfortunately, almost nobody does it.
Almost nobody does it because it's not expected. Why not ask future applicants to bring in some code samples and walk through it?
Well, unfortunately that's not how the interview process is set up (and I personally have many other things to do other than to tilt at this particular windmill). However, post-factum, it seems very natural thing to do - I might probably do it if/when I ever interview for a position where it is relevant (though I might just bring a tablet in and show some code in opensource repose). I don't see why it's not expected - I haven't seen anyone who would find it inappropriate. It's not always possible - some people just don't have code suitable for presenting or sufficiently non-IP-encumbered to present - but if you're lucky to be able to do it, why not?
The best candidate I have ever interviewed (unfortunately, we didn't end up hiring him, but not for the lack of effort from our side) came to the interview with examples of his code and explained what his code does and why he did it this way. Everybody loved that. Unfortunately, almost nobody does it.
Having a place where the candidate shows what he can do - prior to the interview - is awesome, plain and simple. It immediately removes a whole layer of questions for the decision maker - you know who you're talking to, what they are capable of, how they prefer to do it at some level, etc. - and makes the decision much easier to make and less risky.