3 ms·
I have a problem, in that I don't only code at work. I actually code quite often outside of work, but I mostly play with some ideas or implement some simple pro
by skocznymroczny 7y ago
I have a problem, in that I don't only code at work. I actually code quite often outside of work, but I mostly play with some ideas or implement some simple prototypes for games, websites or stuff I am into. But I never really build a product or anything that I'd be proud enough to show in a portfolio, so from a hiring perspective it's as if I didn't code at home at all.
- kennydude 7y agoThere's nothing wrong with including those things in a portfolio at all. You don't need to only list sellable or fully usable products in a portfolio
- iSnow 7y agoParticipating in an existing open-source project can help, as you can contribute as long as you are into it and simply drop out once you stop caring. Your contribution will live on regardless and you can at least show some pull requests and created/solved issues.
- wccrawford 7y agoAs someone who has interviewed a lot of people, those projects do count. If you're leaving them out of your job applications, you're probably hurting your prospects. I'd say to describe them exactly as you have here. The very fact that you're motivated enough to do them is a point in your favor, and if the code looks decent, that's more points. If I compared you to someone else with the same resume, I'd hire you over them.
- gurkendoktor 7y ago> so from a hiring perspective it's as if I didn't code at home at all Even if you don't list them - the knowledge gained from these projects can still shine through in technical interviews, and you can list more languages and frameworks on your CV.