3 ms·
I would also love to know the answer to this. I have an app that is nowhere near what I would consider ideal quality-wise but it's a project that is done, deplo
by stefantheard 9y ago
I would also love to know the answer to this. I have an app that is nowhere near what I would consider ideal quality-wise but it's a project that is done, deployed, and open source. Do I even mention it? I wouldn't as it stands.
- devdad 9y agoI don't know about how bigger firms feel about it, but I'd probably not regard it as a positive. Only show me code you think I'd accept at my work place. For juniors it could be a positive signal though, if you're the kind of person that always looking to learn new things. Depends on the situation if you should show it or not: who are you trying to come across as? If you have the resume, don't show it. Otherwise, do show it and let me know what parts you like and why some other parts are WIP (comments are great here). Another thing to take in consideration is your own criticism. You might be really critical of the project since you're an exceptional programmer, and great programmers tend to move forward quickly and look back at their own old code with distaste. :)
- gitgud 9y agoWell, IMHO it depends on the company, position and interviewer. But something I've learnt is: - Programmers love good code - Entrepreneurs love good products So it's not always the quality of the codebase that matters when showing your side projects. Sometimes the product itself is more valuable.