4 ms·

Even if they dive into a corner of your side project from 10 years ago that works, but you realize isn't ideal, and you don't have the time to improve that part

• 2trill2spill 9y ago
  > Even if they dive into a corner of your side project from 10 years ago that works, but you realize isn't ideal, and you don't have the time to improve that part of the code? Yes, you basically answered the question your self. Tell the interviewer that you wrote that code ten years ago and while it works it's less then ideal, then explain why its not ideal and what a better solution would be.
• wrs 9y ago
  The conversation where you explain what's not ideal and what you would improve based on what you've learned since is why I would want to talk about your side project in the first place. If you said your side project was perfect and couldn't be improved, that would be a major red flag!
• Xylakant 9y ago
  I, as an employer would like to have a conversation about that and I’d absolutely take “I know this could be better, but it was written years ago and it works” as a perfectly good answer. Software can always be better, requirements change and so do capabilities and styles of the people writing the code. But we cannot rewrite all parts of all our software all the time for the sake of molding it to fit our current vision of perfect. Time is limited. Finding the line between “this is not perfect, but it does the job” and “this really holds us back and needs change” is in my opinion one of the most valuable skills a seasoned programmer can acquire.