I know I've said it in a number of interviews and have gotten offers from all but one of them. I don't know if I'd recommend it unless you can follow it up with a strong explanation of why it was the worst -- and how you fixed it -- but it isn't an interview killer, IMO.
I agree with Jeff on this one. Some of my worst experiences with code has been going back over stuff that I wrote 3-5 years ago. I'm pretty hard on crappy developers, so I'm doubly hard on myself when I look back at some of the boneheaded mistakes and decisions I've made.
Comments
I know I've said it in a number of interviews and have gotten offers from all but one of them. I don't know if I'd recommend it unless you can follow it up with a strong explanation of why it was the worst -- and how you fixed it -- but it isn't an interview killer, IMO.
I agree with Jeff on this one. Some of my worst experiences with code has been going back over stuff that I wrote 3-5 years ago. I'm pretty hard on crappy developers, so I'm doubly hard on myself when I look back at some of the boneheaded mistakes and decisions I've made.