I would not worry about what you can’t change, I’d focus your energy worrying about what you can change. That’s where your skills come in. as @psychometry said, companies would be foolish to overlook you if you have the right skills for the job.
Now the skills part is the trickiest. To put it simply there is a lot to learn, and more to learn every day. Unless you a photographic memory, learning all those technologies well in the span of 240 hours is more or less impossible, but that is more or less the bar being provided to you. The fact you actually were able to spit out most of these technologies is impressive. You could spend 240 hours on HTML alone, and have limited job prospects. The fact you went through the course, was exposed to these technologies is part of the learning process, but just being exposed doesn’t mean you have learned it
One of the key parts of learning is knowing what you don’t know. Taking this course and only really feeling comfortable with a few parts of it shows you should learn the rest of the course. You could work on another course, but I’d ask what would that give you? Your missing experience, and the only way you gain experience is by doing. You should start going over the coursework, and figuring it all out on your own time, as the course may be over, but your “learning experience” has only begun.
I usually bring up the analogy of a foot race, where you are running a race, and starting to feel tired and overwhelmed. Someone comes up to you and tells you your not only running a race, but a triathlon, where you need to also swim a few miles, bike a few miles then run the real race, your just warming up! You’d probably be shocked, and might consider giving up and running another “easier” race later. Or you can keep going, grinding your way through the rest of the triathlon and see how far you can get.
Think of taking that course like the guy telling you how much of the race/marathon is left. It might scare you, but without that experience you wouldn’t even know what your getting into, and now you can pace yourself, and have a reference of how far you actually need to go.
Just like a marathon runner, age can be a factor, but I wouldn’t believe it to be a barrier. The biggest barrier is time, and yourself. You need to spend time working with the technologies, and working on your skills to get a chance You also need to push yourself to keep going, because only person can really “disqualify” you from this race/marathon/career change and its you.
Now for your specific questions:
- What is the path you recommend me to follow?
- Build something from the ground up, learn the technologies (or similar technologies, like React instead of angularjs, or nodejs instead of java) the best way to learn is to fail. That’s how you gain experience, not by taking HTML/CSS courses when you want to be a full stack developer (which requires more skills)
- How could I speed up my learning process?
- Again, build off what you know integrating stuff you don’t know but should. Build the app from the course from the ground up, or a new app with newer technologies. Anything, anywhere, just build it and push yourself.
- What country should I move in to get more job opportunities?
The US usually has a lot of opportunity, but remote jobs are popular throughout the world, at cheaper rates.I recommend doing the reverse, where you find a job and relocating to be closer to the job if you get hired. (Be sure to mention you are willing to relocate when applying!)
Depending on where you want to get a job you would obviously want to get the paperwork handled beforehand, so say you work in the US, you can move there ASAP without dealing with extra paperwork, as it could result is not actually getting the job, or a long delay before you can start working.
Goodluck, and remember there is no fast and easy way to success, the best way usually is the steady and consistent approach where you push yourself to learn the topics and learn through failure.
