> But I learn way more if I find a problem I want to solve. Me too, that's why I only keep recommendations in a list, that I don't get/buy right away. However,

> But I learn way more if I find a problem I want to solve. Me too, that's why I only keep recommendations in a list, that I don't get/buy right away. However, many people have lists of 'totally essentials' that I try to read first (e.g. Jeff Atwoods recommending Code Complete) > the moment you buy them you commit yourself to learn something from beginning to end Well, not always, I remember studies (can't find the source) where the majority of the books bought are never even started. That's why I like subscriptions better, where you can just open a book to the parts that interest you. Writing a book involves much more work than a blog post, and it's also motivated by other factors. Specially in technical books, I've heard the rewards are little, so authors usually write a book to gain reputations, which is fine, but definitely requires much more thought and effort, and some times you can tell. Relevant articles by Atwood: http://blog.codinghorror.com/programmers-dont-read-books-but-you-should/ http://blog.codinghorror.com/programmers-dont-read-books-but... http://blog.codinghorror.com/do-not-buy-this-book/ http://blog.codinghorror.com/do-not-buy-this-book/