99% of the time, I've found the official documentation of the language/framework to be enough to grasp most of what's needed so my method is getting down to writing code, keeping the docs close by for reference, and refactoring upon new features learned.

It's worked for me every time, except for C++ and Java, the basics of both of them I was taught in class.

I wish I could select both the others and the online tutorials option.

I would recommend against spending too much time on tutorials. I think an one hour tutorial has usually been enough for me to get started with a language. I've always liked to dive into code head first and learn by making (mostly breaking them in the process) things. :-)

I have four instances I can share:

1. Ruby: When I graduated college, I had to pick-up Ruby. I took a one hour tutorial and asked for code access at my first job and figured out how the simplest of API routes worked. Once that was done, I was given a simple feature which I had to ship the same week. I had it extremely lucky here, given the beautifully simple nature of ruby. It's my favourite language to read code in.
2. AngularJS: A year down the line, I had to become a full-stack dev, so I was asked to learn Angular. I literally had no idea about front-end development, so this time around I took a two day course on Udemy and then jumped into code.
3. NodeJS: Since I've always known JavaScript, I took a direct swing at the code base at my previous job. The code was so beautifully organized that, I could just understand it by reading it and a week down the line, I had already made my first PR.
4. ReactJS: We use React for the front-end here at Hashnode and I didn't know anything about it when I joined here. As usual, I jumped into code and for the first time ever, I found it rather difficult to get hold of things. React was like nothing I've worked with before, so jumping head first into code was a real trial by fire for me. However, thanks to my amazing co-workers, I didn't really need a tutorial. I tried to build some small features initially and since I didn't have a formal introduction to React, I was writing code in React like how would in Angular. My PR's got quite a few comments in the initial days, but I feel I am finally there now.

TLDR; Don't spend too much time on tutorials, just get hold of the syntax and the concepts and dive into code. More importantly, read code and understand how it works.

I think there are two funnels to this-

1) You want to learn it for yourself (Online Tuts)

2) You have to learn it for your project (Documentation/Reference)

For me, Tutorials are awesome across the board to see someone who's experienced speak to their real-world examples and concepts that you might not have thought of. Gives insight to possible best practices and "gotchas".

On the other side, you might have a particular project where you have a roadmap, specs, etc, and can get right into the Documentation to accomplish it. In most cases, I'm doing both #1 and #2 above.

I just get started and Google the bits I don't know. Then after about a month of hacking and Googling, only then do I read a book or the docs back to front.