Maybe business books are just different than technical/science oriented ones.
Maybe business books are just different than technical/science oriented ones.
10-20 minutes won't cut it for deep technical material, particularly if the book is designed to teach via working through examples. If you're reading a workbook, then take the time to work through the examples. Choose your workbooks carefully, since they require a more significant time investment.
Most non-fiction books, however, are written around a few simple, straightforward concepts - you can identify them in a few minutes. A few more minutes identifying examples, relationships to other concepts, and counter-examples / edge cases, and you've extracted 90% of the value of the text.
Almost every non-fiction book fits this model. It pays to tailor your reading approach to what you're reading.
As to value - in general, most business books are marginally valuable in isolation. Once you read many of them, however, very useful patterns begin to emerge. Recognizing and using those patterns provides the value.
I'm at the point where I can sometimes skim through arXiv papers and understand the gist.
(Does it work the same for books with code in them? Legit coders can skim and understand?)
Since they're not actually written in PHP, I've got to switch to a new language. ObjectiveC for iPhone, Android-Java, or any number of cross platform languages to pick up a third party framework.
On top of that - there's the issues of structure and stuff.
For learning a new language, there's no way to skim.
HOWEVER for something like an A* pathfinding algorythm (an artificial intelligence method of finding the most efficient path from A to Anywhere) - you can get the "Gist" by skimming a paper. I understand what A* is and how it does it ... but if I want to replicate it I still have to go over it line-by-line if I want to get it right though.
So, I think the short answer is "NO" coders can't skim stuff and get the job done right.