It is not like studying a course in a organised way.. Luckily we switched to microservices architecture in my company and thus many stuff had to be rewritten. The old monolithic application was PHP and PHP was deprecated for new projects company wide. So I and my team picked GO, JAVA and Node.js for different microservices we are responsible for. (Mainly JAVA and GO, we deprecated then Node.js unofficially in our team because we did not like it at all.) So as you have a well defined project and you have to finish it in the language you are new with, you start to research and learn a lot. Tutorials, blogs etc. And when I had a problem and I could not solve the problem because of my unfamiliarity in the new stack, I started to read also after work and I started to apply what I learnt the next day. Every day I started to have less problem or finding solutions was taking less time because my involvement in that ecosystem increased. Specifically for JAVA, probably still I do not know many stuff, especially I don't have so much idea about the abandoned enterprise technologies, or legacy build tools like Ant etc. but still our applications have good quality and they are working well and my team did not receive any bad feedback from JAVA-expert fellows from the company, it means we adopted well the technology and caught the train.

I've to open a new paranthesis about Node.js. If you've never worked with Node.js before and you start in 2016 you're kinda f*cked up. The ecosystem is changing a lot and maybe 70% of the resources you can find over internet are already outdated. You start the day happy and with full batteries and you start to use some frameworks etc. The next day you realize that people already abandoned it. Beside all the disadvantages of Node.js, it's also so annoying and make the adoption process so hard. How such a simple language like Javascript could become so complicated?

GO is very cool. Relatively easy language and also very very powerful, it has a high quality community and the resources you can find are very clear. If you are trying to pick between GO and Node.js, go with GO. Your adoption will be much easier.

Yeah. I agree. I dont understand how people build large Node projects.

Thanks for the tips and insights, man! You were lucky to be in a project willing to rewrite the monolith with different technologies.

By the way, looks like you're living in Barcelona as well ;)

I used to live in Barna for a couple of years. Now in Berlin :)

> Specifically for JAVA [...] abandoned enterprise technologies

> [...]

> How such a simple language like Javascript could become so complicated?

;)

Well, let's admit that release-abandone cycle for a library/framework/approach in JS world is 100x faster :)