I feel like we'r missing an option "create a sample project" . Thats my go to technique.

Would you believe me if I told you that I learned many languages, studied technical engineering and computer science and work as a Web/C# Developer for a big company atm. without ever taking up a single book or watching a video? Because that's a fact. I learned everything I know by reading docs and trying out stuff on my own. The most important part of the docs is the "Getting Started" section, and from there I go and google everything I need and do not know. I do not believe in learning from videos. Who made the video? How much do they even know? Are they certified? How well did they prepare the video? Can you remember all the important (theoretical) stuff just from hearing it? But with docs you know that someone wrote it who knows what they are talking about. Because that's the way I learn, my latest project is building a specialized game engine directly on top of Vulkan. Yeah, there is no documentation, only samples. But what about it? I am used to read source and try stuff out myself.

My preferred way: Build stuff with the new technology, consult the docs or the source code of the technology as the need arises.

I have a really slow Internet connection, so it's mainly books for me. Or e-books on my e-reader. Or online docs that I've converted to ePub with the GrabMyBooks browser plugin.

Reading books (even converted ones) seems less rushed than reading stuff off a computer screen. So I usually do that to get familiar with the concepts. It also helps me get an idea of what features are available, and what the common development patterns are. After this, I draw out an idea for a project I want to make.

Once I have a plan, I have the usual online docs, example code, and StackExchange Q&A to help me while I'm actually coding. git init and I'm ready to go 😉

Documentation is step number one, particularly the code examples. If things don't entirely "click" or I can't see the practical application of a new technology, I go to the videos.

The reason I chose screencasts is because usually people make it with a lot more detail or just do it from scratch and see everything you need to do to start running the plugin, the code, and everything because they record their screen and explain everything they do. But when you're reading documentations, there's a lot of people who is lazy to explain everything and miss a lot of important things and you have to do a lot of research for specific situations that should be common but find the answers on forums, blogs, etc; everywhere but the actual documentation and a lot of times what people do with their plugins is say well this plugin does a lot of things but the documentation is a mess or just simply don't explain all what it can do with reasonable detail.

I chose screencasts but I actually prefer just diving into it.

Other - Theres a mantra / saying that I believe originated with physicians (so far as Google can tell me anyways)

Watch one. Do one. Teach one.

Watch someone do it - be it a video or written guided tour.

Do it - take what you saw / read and do it.

Teach it - usually as simple as trying to explain to a co-worker or my wife what I just did - this helps validate what I just learned and by telling someone, helps me put the pieces in the right order.

Works for me anyways.