I don't typically find tutorials as such to be that interesting. As has been said before, this really comes down to the way that you learn. What I do is:
- Find something I want to learn--this part is usually incidental or accidental. I see it, it sounds nifty and I make a note to get back to it.
- Devise a project to exercise that technology. For example, I decided to write a console version of Tic-tac-toe to learn Haskell.
- Pull up a few articles and skim them really fast. No dedicated back and forth, just a quick overview. Enough to get the feeling that I know where to start.
- Start working on my little project. The outcome of this is that I am forced to revisit tutorials and re-read the portions that hadn't quite crystallized in my head.
- Rinse and repeat. I read the parts that didn't entirely make sense and keep refining my sample project.
One of the useful things I find about this process is that of feedback. Reading tutorials and staying on the rails has something of a coerced success/failure. My mistakes were those that the author told me to make, not necessarily the ones I would have made. On the flip side, the things that worked were only the ones that the author meant me to see.
By diving in (over my head, by design) I get rapid feedback. "I understood X, no need to keep reading on it." "Y didn't make sense--better read a couple more articles on that". It also avoids some of the Ivory tower syndrome. Even the smallest hint of the real world will rapidly tease out good and bad things about what it is you are trying to learn.