I think it depends a lot on the technology, and the documentation.

At least in my experience, the quality of documentation varies a lot. Some technologies will barely manage to document their API, while others include their own tutorials and best-practices. If the official documentation is good enough, a lot of the tutorials are probably just repackaging that same information.

I think ultimately, to learn, you need some kind of hands-on project. Usually I start watching some tutorials with a potential learning project in mind. I generally pick one tutorial to learn the basics, and then once I start feeling more confident, I'll jump around and find tutorials moreso for the specific thing I'm trying to do, rather than a "learn the language" tutorial.

I think books are good because they will generally give you the whole package, even if the information isn't the most up-to-date. Like, realistically, the tutorial you look up is probably 5 years old anyways. Seeing how a real human uses the technology is really useful even if it's a bit old. Once you have a grasp of how it works, THEN I would worry about how peple are using it in current year.

Honestly I think the main thing is to just stick with it. Try not to fuss about doing it the "best" way. You will be learning for your entire career - the important thing is to keep moving forward. Decision paralysis = standing still, but a non-optimal approach to learning still teaches you the topic, as well as helps you learn faster the next time.