Even bad code would make for an interesting discussion topic during the interview. The code may turn out not to be as stupid as the interviewer thinks after all

Even bad code would make for an interesting discussion topic during the interview. The code may turn out not to be as stupid as the interviewer thinks after all. Or maybe it is, in which case it's great to talk about lessons learned. I think every developer has some bad code floating around out there, including the person conduction the job interview. They'll understand. And if they don't, that's a great litmus test for the type of company you are applying to as well.