I suggest specialization. If you're 80% as skillful as necessary to make an impact at 8 different skills, that means you make an impact at nothing. If you're good at one thing and very green at everything else, you're employable.<p>It's great that you have some experience with C and that will give you a perspective on how things work at the machine level, but my advice would be to go the opposite direction. As a junior, the area of the stack where you can most quickly prove your chops and where you'll get the most companies willing to trust you is probably going to be the front-end of the front-end.<p>If I were you, I'd learn CSS and a framework (preferably Tailwind) well enough to clone any design you see on the web. I'd be cloning a different site every day. Of course JS will help too, and pick up what you need, but I'd stay laser focused on getting good at and fast at building any responsive site you see. If you can do that, you'll have no problems finding work. After half a year or so on the job, you can start working down the stack and getting better at JS and then databases and other technologies.<p>Also, I'd put about 10% of my time (and I still do) into improving with workflow related tools, like your editor, git, the browser console, etc, etc. It adds up over time.