
The Reading Mind
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Person
Content
Introduction
The Chicken Milanese Problem
Agenda for the Introduction
To consider the question "how does the mind read?" More specifically, to understand why it is a terrible scientific question, and why we pose it anyway.
Picture this commonplace scene. I was on an airplane, reading E. L. Doctorow's Billy Bathgate on my Kindle. The following passage is found near the end of the book, and when I read it, I softly gasped.
Before he got through it I was hearing the distant sound of police sirens, and it was so arduous for him to speak it that he died of the effort: "Right," he said. "Three three. Left twice. Two seven. Right twice. Three three."1
My goal in this book is to account for what happened in the few moments it took me to read those 43 words.
The environment held nothing more remarkable than black marks on a white screen, yet somehow I was mentally transported to another world, indeed, to a world quite alien to me: New York City some 30 years before my birth, populated by gangsters. How does the mind create a mental world from black marks? And why would I care enough about Otto "Abbadabba" Berman-a real-life gangster portrayed sympathetically in this novel-to gasp when he's murdered?
The approach I'll take to answering these questions is cognitive. I'll describe what the mind is doing as we read, but I'll seldom consider what the brain is doing. That may sound shortsighted (the mind is, after all, what the brain does), but it's a common scientific approach taken over the last fifty years. Computer science offers an analogy. You can describe the steps of a calculation-say, figuring out the date of the next lunar eclipse viewable in Toronto-without describing what's happening in the electronic guts of the computer during this calculation. In the same way, I'm going to describe the steps by which your mind reads without specifying how the brain carries out those steps.
Cognitive psychologists commonly tackle large, daunting questions by breaking them down into smaller, more manageable questions. We do that by thinking through what had to happen in order for some bit of mental work to get done.
What had to happen between my seeing the letters on the screen and my emotional reaction to the events in an imagined world? I had to see the letters and identify them. I had to assemble the letters into words, and then the words into sentences, which I comprehended by applying grammatical rules. My emotional reaction entails not just comprehension, but memory. "He died of the effort" prompts pity only if you feel like you know Berman. So over the course of the novel I must have built and updated a sort of personality picture of this character. And of course memory is needed to organize the sequence of events into a coherent sense of the plot.
So, will this skeletal outline of what happened as I read Billy Bathgate serve as a starting point for a theory of reading?
How Do You Make Chicken Milanese?
Even my crude analysis shows that "what happens when we read?" is a bad scientific question, the type of question psychologists usually don't pose. Why? Think of all the millions of activities your mind can direct: you can guess the cost of a paperweight you see in an antique store, ride a child's tricycle for comic effect, make Chicken Milanese, invent a plausible excuse for missing your neighbor's son's middle school play, and so on. For each of these we might pose the question "What's happening in the mind when you do that?" But scientists don't. The reasons that scientists don't ask how you cook Chicken Milanese inform what I've included and excluded in this book, so it's worth describing these reasons in some detail.
The first reason is that task descriptions are not quite as simple as I've made out. I said "let's consider what had to happen" as I read that passage from Billy Bathgate, and then I said something like "you have to perceive the letters, and understand the words," and so on. The history of psychology shows that it's easy to be fooled when you try to describe a task.
Here's a simple example. When we read it feels as if we move our eyes smoothly-we sweep from the start of a line to the end, and then snap back to the far left of the page for the next line. That impression is easily disconfirmed by watching the eyes of another person as she reads. Her eyes don't move smoothly, but instead jump from one spot to the next, usually a distance of seven to nine letters.2 That's so easily observed it's probably been known for centuries. But even that observation-jumping movements, not smooth tracking-is an incomplete description. In fact, your eyes are not always pointing at the same letter when you read.3 About half the time each eye looks at a different letter. They may even be slightly crossed.
The implications of this fact for an understanding of reading are not obvious. I raise the issue to point out that researchers have been working at an account of reading for over a century, and they are still finding ways of improving their description of what's actually happening when someone reads-not how they do it, but what they are doing. That's one reason psychologists usually don't try to explain really complicated behaviors. They figure that they probably shouldn't be confident they can adequately describe what they are explaining.
Suppose we give up on the idea that we'll have a perfect description of what people actually do during a complicated task, and we decide to settle for a provisional description. That's not a bad strategy-as we learn more, our description of the task will improve. One thing we're pretty confident about is that a complex task will require many different cognitive processes. My off-the-top-of-the-head analysis of reading called for vision, memory, grammatical analysis, language comprehension, and emotion. Any one of these mental processes is known to be terribly complicated.
Consider seeing letters. One challenge is that letters can take on quite different appearances, varying in size, typeface, and typographical emphasis (bold, italic, etc.) (Figure I.1). How does my visual system treat these very different-looking objects as equivalent?
Figure I.1. One letter, different fonts. These letters must all be interpreted as equivalent, even though they look different.
© Daniel Willingham
Worse yet, the very same shape might be interpreted as representing different letters, depending on the surrounding context (Figure I.2). So we need to do more than define what makes an "A" an "A"; we need to specify the context in which it will be seen as an "A."
Figure I.2. Ambiguous letters. Although I'm sure you read this sentence easily, if you look closely you'll notice the "e"s in the word "need" are the same shape as the "c" in "clean." And the same shape is interpreted as a "v" and as a "u" in the word "volunteer."
© Daniel Willingham
Finally, note that we've taken for granted that we're looking at black characters on a white background. How could it be otherwise? But what dictates that "the black bits define the objects, whereas the white is background"? Differentiating objects from their background is so embedded in our visual system that we seldom notice that it's an issue, unless we're looking at one of those clever images where the object and background are ambiguous (Figure I.3).
Figure I.3. Reversible figures. At left, the black area can be seen as an object (vase) and the white area as background, or the white area seen as the object (dog profiles) and the black as background. At right, the mirror is seen as background when we focus on the woman and her reflection, but it may also been seen as the foreground object-a skull.
Vase © Tasha Volkova via Shutterstock; "All is Vanity" by C. Allan Gilbert. Public Domain http://bit.ly/2a2Nddd
Now suppose the complicated work of identifying letters is complete, and I've assembled the letters into words. My mind is trying to sort out the meaning of what I've read. One problem is that some words have multiple meanings. In the Billy Bathgate passage, Berman starts his brief speech with the word "Right." What did I think he meant when I read that word? Morally correct, as in "the right thing to do"? Or perhaps agreeing with the facts of the matter, as in "You got that right." Or appropriate, as in "the right tool for the job." A few words later Berman uses the word "left" and so it becomes clearer that when he said "right" he was probably signifying a direction. But before I read "left," what did I suppose "right" meant? Did I suspend judgment, hoping for clarifying information later? It doesn't feel like we do that. For example, if you read,...
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.