There is a lot of good advice here. I would do the second, if not all.
Based on my experience, I would suggest choosing three languages. I would choose the one that seems the most accessible and useful for studying in the first place, and familiarity with the syntax is good enough to be able to identify problems with existing code, but don’t feel that you need it to get used to the point you write expert, error-free code from memory. Use your documentation and link as a floating device during work and training. Spend more time mastering concepts ... especially debugging! And jump and try, even if what you start first is really bad or doesn't work at all. (I feel that the ideas that are most solid in my head are the ones that I almost killed trying to fix, not learn, carefully study the ideas before trying to code.)
Once you have a good language, move on to the second, perhaps syntax, which is different from the first. This approach made me aware of the concepts and confirmed that I didn't need to be a syntax expert to get the job done. In the end, there are usually tons of documentation, textbooks, and discussions available to everyone.
Then take the third language and immerse yourself in it. You will be surprised how much easier the third. You will see the middle ground, syntactic, between the two extremes that you have already learned, and as very similar programming concepts.
If you want to be extremely competitive and competitive, you can choose your languages based on diversity: for example, one that is good for the Internet on the client side, one that is good for the server side, and one that is good for the platform / device development. Or, choose languages based on the fact that you know that you will like the building. I found this to be the most effective and interesting; that is, if you know that you are a game fanatic, just learn the languages that will allow you to create and transfer reliable games to different platforms and keep the focus.
Finally, don’t press on yourself, comparing yourself to other developers and feeling that you need to be like them, or find out what they did, the way they did, as fast as they did. Experiment and find out what works for you and stick to it.
Just my two cents. Good luck