1) There are a lot of development-related things that I simply want cursory knowledge about right now. Blog posts, textbooks, and the like are great there. The way I go about things is to maintain a list of books to buy and buy them on a FIFO basis. Typically there is about a year lag between when a book goes onto the list and when it comes off and is purchased.
I then work through the book read it, etc. Go on to the next. The book then goes up on my reference shelf and I can go back to it when I need to.
The second group of things I need to learn I have strong knowledge in a related area and really need to work with someone to solve a particular problem. Niche areas of accounting (I maintain accounting software) is a good example of this. I bring myself up to a "conversational" level of knowledge, then work with a customer's accountant to make sure everything is implemented right.
But keep in mind I read about 100 textbooks a year and only a small minority are on IT. Most are hobbies (archaeology, linguistics, history, anthropology, and the like are big topics). It is easy to work an approach like this in.
Hmmm on reviewing the books I have read, it seems my original list included some things that should not have been there. A quick assessment of ratios suggests I should drop it to 70-75 per year.
If it's more light reading or less foundational I can do a bit less than page a minute. This week I trudged through EffectiveUI pretty mindlessly (a lot of O'Reilly books are very wordy and soft) in about six hours.
That is one reason for serious learning I use textbooks. The book itself helps structure your learning, it is easy to keep track of how much you have covered, and commitment is simpler, since you can just commit to finishing the book.
It doesn't help as much though for longer term learning; I have a tendency to procrastinate between books, and often switch directions and even fields of study. On the other hand, the OP's "learning list" doesn't help much with that either.