> so i try to work on things like a compiler and a real-time rendering engine
Even unfinished this sounds like a cut above the average entry level dev. Make sure these projects are on github or whatever so people can see the code, even unfinished, it's good to see the progression.
Apply for a dozen junior dev jobs and see what happens. You'll probably get a bunch of rejections, but if you can write coherently and talk clearly you've got a chance.
And even if you don't get one you will probably discover something about what it is you are missing that businesses want and you can work on that specifically.
I missed the edit window, but the post got me thinking, so I came back to add this.
My first dev job was straight out of uni. No prior work experience, and no open source work to share. I had a 2000 line final year project written in c++ and that was it.
I think may 1% of the graduates had any open source contributions. Most were like me.
If you consider that these will be the people you are competing against for a entry level role. Your projects are a huge thing if you open source them, even unfinished. Just demonstrate an understanding of some CS concepts, algorithms, code design, etc and you'll be competitive at the very least.
Even unfinished this sounds like a cut above the average entry level dev. Make sure these projects are on github or whatever so people can see the code, even unfinished, it's good to see the progression.
Apply for a dozen junior dev jobs and see what happens. You'll probably get a bunch of rejections, but if you can write coherently and talk clearly you've got a chance.
And even if you don't get one you will probably discover something about what it is you are missing that businesses want and you can work on that specifically.