They probably wont be looking for perfection, more likely they'll be looking at how you work, your logical approach and ideas.
If you're showing a home project you've been working on, it's perfectly acceptable for parts of your code to be work in progress. If things need to be improved and you don't have time to do it before your interview, then notate what needs to be done and be open about it - Show that you are aware of priorities.
Most of all though, just show a bit of passion and interest!
If you're showing a home project you've been working on, it's perfectly acceptable for parts of your code to be work in progress. [..] Show that you are aware of priorities.
100% agree, with a special accent on the priorities part. I'd always take a dev that knows how to choose his priorities over one that "perfects everything" (whatever that even means).
That said, I think that you should have at least some part of the code sleek and well tested, just to show that when you eventually put a priority on something you do it well.
Priorities are super important, yes. I have a lot of things/bugs shoveled into the backlog, including tests on many non-critical parts. Otherwise, nothing would be working even at this point.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'd go further, and say that parts that are work-in-progress or otherwise buggy are important, because you get to talk about them. You get to talk about how if you started from scratch you might have done something differently, and which problems you are prioritising, and why.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Anna,
They probably wont be looking for perfection, more likely they'll be looking at how you work, your logical approach and ideas.
If you're showing a home project you've been working on, it's perfectly acceptable for parts of your code to be work in progress. If things need to be improved and you don't have time to do it before your interview, then notate what needs to be done and be open about it - Show that you are aware of priorities.
Most of all though, just show a bit of passion and interest!
Good luck and all the best.
Thanks a lot! It gives me more confidence.
100% agree, with a special accent on the priorities part. I'd always take a dev that knows how to choose his priorities over one that "perfects everything" (whatever that even means).
That said, I think that you should have at least some part of the code sleek and well tested, just to show that when you eventually put a priority on something you do it well.
Priorities are super important, yes. I have a lot of things/bugs shoveled into the backlog, including tests on many non-critical parts. Otherwise, nothing would be working even at this point.
I'd go further, and say that parts that are work-in-progress or otherwise buggy are important, because you get to talk about them. You get to talk about how if you started from scratch you might have done something differently, and which problems you are prioritising, and why.