Reading Levels: Different Ways to Read Different Books (2018)
thecuriousreader.in
thecuriousreader.in
A similar effect can be found with Grit, Fogg’s Behavior Model, Superforecasting, and most Gladwel books.
On the coding side, I’ve only noticed this with Pragmatic Programmer, Clean Code, and maybe Phoenix/Unicorn project. Could I don’t read enough of those or they’re too focused on specific technologies instead of broad ideas … or I get too much of my technical reading from blogs and twitter. Those do get repetitive and you quickly find common patterns, but no titles to refer to.
And then you start to question all the knowledge you thought you’d gained from the books you read that weren’t “the” books.
It’s similar to being an expert in a field and shaking your head when a newspaper article completely butchers that subject. Do you then still trust that newspaper’s articles on anything else?
My take of Adler's method is that, if you can't find a new message in the books you are reading either: 1) you aren't putting enough effort in your reading 2) the books are not good enough (hence not worth your time to read)
https://en.m.wikipedia.org/wiki/Michael_Crichton#GellMannAmn...
My observation has been that theory of constraints is a hidden secret in engineering and most people instead refer to the devops/phoenix version of it.
You just read in depth different approaches to the same / similar problem. At some point you build experience and you can classify fast a new publication as good or bs.
The in depth studying of a critical volume of literature is a prerequisite for one to build an understanding of what is worthy and what is trash.