Here is a revised version of your plan that I recommend. I don’t work or hire in the industry, but I’ve been doing this for about a year, and I have some insight that may be useful. (Btw, I’ve also been a full time student and small business owner, not eager to go to work for someone else during the last few months.)
FreeCodeCamp- going through the exercises and challenges.
Any number of other resources including w3schools- to supplement, clarify, or reinforce learning.
Personal projects during the whole learning process- Start ASAP, this is where it really all begins. This is the ? which holds the beanstalk which rises to the clouds full of shiny golden coins and dreamy music.
Meetups- They’re laid-back and most people aren’t experts and there are usually people who know nothing at all. So if you know something, you’re ahead of the game. Nothing to fear but boredom.
Contribute- to open source project(s)
THEN decide if you still want to get into:
- QTP, Selenium IDE and Selenium WebDriver, Cucumber (BDD Framework) , TestNG ( to cover all categories of tests: unit, functional, end-to-end, integration etc.) for the software testing path.
Here’s why the rest of the list was scrapped:
Node, Express, Mongo, jQuery, React, GitHub- Already covered in FreeCodeCamp.
Python, C#- Python you might pick up, but I’m not sure where it fits in the plan yet. C# is part of .NET, a year’s worth of study on its own. I wouldn’t treat it as a mere component of a year-long plan unless your plan is to play around with a bunch of languages for fun (which is fine, but you want a job sooner rather than later).
Angular, Ember- See how things go with JavaScript and React first. To plan on learning frameworks that could be on their way out in 6 months, before you’ve even conquered the fundamentals of the underlying language, is a plan crafted in Front End Developer Hell.
Java, Android- I’m not saying don’t, but I just wouldn’t have it in the plan yet. Much like .NET/C#, it’s a pretty big commitment for something you know little about, especially if you’re paying for the courses.
Real experience, etc.- We’ll see after you’ve built some original personal projects. I think working for free on interesting open source projects will be much better for you and your resume than competing for the chance to work for peanuts on those sites.
The reality is that you have a hell of a lot to learn before any plan makes sense, and everything will probably change within the next month, not to mention the next year. But this… might come in handy at some point. Thank you for listening to my story.