Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
neeno34081yIf you're this concerned about how good your code is, it's probably pretty good. I don't have a lot of experience but I'd say you should just get out there and apply for some positions. What's the worst thing that could happen?
Do some interviews and explain this to the interviewer, show your passion. You don't have to have a lot of experience or any finished projects in your portfolio for entry level positions.
EDIT: also I'm not sure it's a bad thing to have ended up in bad terms with your old company since it was their fault, not yours. Don't mention it, but if they ask you about it in an interview just tell the truth. Not sure if it's the best way to go, but that's what I would do.
EDIT2: take everything I say with a grain of salt, I'm still an intern in my first job ever so I have almost zero experience.
Don't worry too much, like @neeno said, start racking up interview experience. Maybe start with offers that are not very interesting to get the hang of it and not burn good offers.
Not graduating shouldn't be a problem in our field. All good.
Make your private project public and archive them right away. It's a good way to show something yet state it's not being maintained anymore and should be taken with a grain of salt.
We all had bad experiences, unfortunately. It's all good, don't hide it. Don't immediately speak about it but if asked, build a narrative that's vague enough your interviewer won't think you're a bad apple.
Remember it's a two-way process, you interview a company as much as they interview you. Bad experiences are useful to direct your search in the best match possible. Eg. If they had a mismatched employee, they might look for red flags linked to it. You do that too.
We don't always match and you discover that afterwards.
All good. Keep up.
Nihil755961yAs someone that's hiring I prefer to see a GitHub profile with many repos than an empty one.
Bad code quality is a warning sign for more senior developers (I usually look for tests), but with junior ones less so, and if it's very diverse and shows interest in broad-spectrum of things it's a huge plus. even unfinished.
Thank you all for your advice and words, I made my older repos public, and will keep on working on my current project so I can show it off