This would be my recommended approach as well. Think of a project you can build with the technology you want to learn, and then learn the technology through ac

This would be my recommended approach as well. Think of a project you can build with the technology you want to learn, and then learn the technology through actually building the project. I generally feel more motivated with this approach because at the end of the effort, I'll actually have something to show for my time. If the project idea is good enough, you might even be able to turn it into a business, but don't let the lack of good ideas stop you, because your primary goal is still learning, and for that, even clones of existing products can work (and you might be able to find a good twist on it that can differentiate your own project as you build it). And for me personally, no amount of reading and exercises can compare with real usage if I wanted to become truly proficient at a technology.