Search this site: [Advanced Search]
 

Messages: 3 of 3. Pages: 1
Comments/Replies (2) appear below in chronological order. Comment form is at bottom of page.
How To Read A Book (#1837)
Posted: 10/2/2005; 1:16 PM by Terry Frazier
Reply | Trackback URL | Weblog Permalink
cover_big.jpg Mortimer Adler and Charles van Doren’s book on reading methodology never fails to draw a laugh when I take it out in public. Yet it’s one of the most useful, and well-used, books on my bookshelf. This is a practical book, filled with solid, step-by-step instructions to help you read quickly, actively, and effectively. Adler’s approach can be summed up as “Don’t focus on reading everything as fast as possible. Rather focus on knowing the right speed, and knowing which material should be read each way.” Among the topics covered:

  • Inspectional Reading
    • How to read any book in 30 minutes or less
    • What to read during this stage
    • How to find the key points
  • The four questions every reader should ask
    • What is the book about as a whole?
    • What is being said in detail, and how?
    • Is the book true, in whole or in part?
    • What of it?
  • Analytical reading
    • Categorizing and X-raying a book
    • Finding the key terms and understanding them
    • Finding the author’s message
  • Criticizing a book
    • Agreeing or disagreeing with an author
  • Note taking, “tagging” (in the offline sense), and making a book your own.
  • Building a reading framework
  • Syntopical reading
    • Understanding the conversation between authors
    • Finding the relevant agreements and disagreements between them

Over the years I’ve read a number of books – by Colin Rose, Bobbi DePorter, Tony Buzan, Joyce Wycoff, and others – that claim to improve reading speed and comprehension. Though each of them provides useful tips, none offers as thorough and effective a framework as Adler and van Doren.

But detailed frameworks are not easy to master. I frequently find myself taking the book out for reference, even though I’ve read it a number of times. Each time I read, or re-read, a particular section, I come away with a new insight about how to evaluate, critique, or compare books. To me, this is the hallmark of a great book.

The latter sections of the book contain instructions on applying Adler’s process to specific types of reading – non-fiction, imaginative literature, stories and plays, history, science and mathematics, philosophy, and social science. If I have never read, or haven’t read in some time, one of these genres it’s helpful to review just the section on that genre before I start.

Be aware of the book’s style as, at first, it can be a bit off-putting. While not a complex book, it is written in classic prose – that is, it’s somewhat verbose. Today we would call it “over-written”, but it was originally authored in the 1940s, and updated in the early 1970s – well before the modern, web-centric era of short, pithy text and summaries. This doesn’t bother me. I still find Adler’s erudition and style entertaining. But I recognize it may bother some readers. Still, I think it worth working through if your goal is to be the most effective reader possible.

The book could easily serve as the text for a semester-long course in effective reading at the high school or undergrad levels. I wish I’d had such a course. If Adler’s techniques were taught to all high school students we’d have a far more literate and thinking population than we seem to have today.

Even if you live in the world of the web, Adler’s techniques for deriving the author’s meaning, understanding propositions and assertions, and thinking critically about what is said are valuable. They can help you avoid the common confusion between a fact and a mere assertion, and better question whether the author has used sound logic.

RE: How To Read A Book (#1846)
Posted: 10/5/2005; 6:58 AM by David C. Buchan  In Response To: 1837
Reply form is at bottom of page.
Terry,

Can you explain further how this book helps you specifically. One more book for me to read and I'd like to hear more of the day-to-day practical benefits.

David

Practical Application of "How To Read A Book" (#1848)
Posted: 10/5/2005; 11:37 AM by Terry Frazier  In Response To: 1846
Reply form is at bottom of page.
On 10/05/2005 David Buchan wrote:

Can you explain further how this book helps you specifically. One more book for me to read and I'd like to hear more of the day-to-day practical benefits.
Succinctly, How To Read A Book (HTRB) is a tool for reading difficult expository works. Adler, being borne of the encyclopedic era, was quite old school and spent a lot of time on the works of Plato, Aristotle, Mill, Locke, et al. In HRTB he shares the methodology and process he used for understanding them, comparing them, and vetting his own ideas and conclusions.

Much as Getting Things Done offers a framework for managing and prioritizing competing tasks, HTRB provides tools to manage and prioritize competing ideas. Also like GTD, the framework is intended to be active - that is, practiced in the pursuit of something else. For Adler this something else was understanding the relative merits and importance of arguments put forth in writing.

Today I keep the book around as a check list, to make sure I covered all the bases if I'm reading something important. It's most useful when I dig into a complex topic like privacy, identity, or copyright law where lots of people have strongly held, conflicting opinions. And where separating fact from opinion is challenging. Socio-cultural issues are another area. The conflicting ideas of people like William Henry (In Defense of Elitism,) Alfie Kohn (No Contest,) Robert Sheaffer (Resentment Against Achievement) are not at all helpful unless you can put them in context, vet them, and know why you agree or disagree. As Adler says, "The person who says he knows what he thinks but cannot express it usually does not know what he thinks."

If you read lots of fiction or literature, where the goal is entertainment, you don't need HTRB. Likewise, if you read mostly simple books, or only one book on a topic, you won't usually want to invest the time the HTRB process takes. Where it shines is when you read a lot, and read multiple books on a single - or similar - topic. His idea that "reading should be a conversation between you and the author" only works when the author is trying to convince you of something. Adler's process ensures there's some rigor in that conversation. Frankly, Adler's reading process is more rigorous than many author's writing process. And, if used consistently, would probably lead to debunking the vast majority of books on today's bookshelf. But that's beside the point. The point is Adler gives you tools to be able to figure out for yourself whether a book is really worth reading, and to know you understand what it means when you're done.

Most useful to me have been the chapters with step-by-step instructions, such as Chapter 5 - "How To Be A Demanding Reader" - wherein Adler offers specific rules for "active" reading, as well as questions to ask and techniques to use at each step.

  • The four questions a reader should ask
  • How to make a book your own - conversing with the author, marking, thinking
  • Three kinds of note-making. Different techniques for inspectional, analytical, and syntopical reading - structural, conceptual, dialectical
Also Part Three (Chapters 6-11) on analytical reading, criticizing a book, and agreeing or disagreeing. Adler offers 11 rules in this section:
  1. Classify the book according to kind and subject matter
  2. State, briefly, what the book is about (doing this is actually hard)
  3. Enumerate the major parts and outline them as you have the whole
  4. Define the problem, or problems, the author is trying to solve
  5. Come to terms with the author by interpreting his key words
  6. Grasp the authors leading propositions by dealing with his most important sentences
  7. Know the author's arguments by finding them in, or constructing them out of, sequences of sentences (not paragraphs)
  8. Determine which of his problems the author has solved, and which he has not; and as to the later, decide which the author knew he failed to solve
  9. Do not respond until you understand
  10. Disagree reasonably, not contentiously
  11. Respect the difference between knowledge and opinion by giving reasons for any critical judgements
I don't do all of these every time, as most books aren't worth the effort. But the nice thing about the framework is you apply it only as much as required. From scanning, inspecting, and analyzing to comparative research, just use what you need.
Total Messages: 3. Pages: 1

Trackbacks

What other weblogs are saying about this topic. Trackback URL: http://www.terryfrazier.com/1837/trackback

Reply to message #1837...

You must logon before posting a reply

You must login to your account to post a comment. If you do not have an account you can create one here. It's a bit inconvenient but only takes a moment and helps control spam and other bad actors.