Transcript

Use with ChatGPT / Claude Auto-scroll A

1. Sokal Hoax and Intelligence

The transcript opens with Alan Sokal's deliberate hoax and the controversy it caused in academia. It then raises the central question of how we tell the difference between real intelligence and language that only sounds smart.

0:00 - 0:56
In 1996, a physicist at NYU named Alan Sokal convinced an academic journal to publish a paper that he had deliberately filled with a bunch of nonsense.He called the paper Transgressing the Boundaries Towards a Transformative Hermeneutics of Quantum Gravity.And if that title makes little or no sense to you, then that's sort of the point.The article mixed real physics with a bunch of false claims, unsupported leaps in logic, and sentences that Sokal later admitted didn't mean anything.You see, he had written the entire thing as kind of an experiment.He wanted to see whether a journal would publish an article filled with a bunch of nonsense if the article sounded impressive and told the editors basically what they wanted to hear.And sure enough, a cultural studies journal called Social Text included it in a special issue about the conflict between science and cultural studies.
But on the same day that the article appeared, Sokal revealed that the entire thing was just a hoax, which sparked a massive public controversy in academia.Now, to be fair, the editors of Social Text disputed what Sokal thought he had proven.They pointed out that their journal wasn't a peer-reviewed science journal, and they just wanted to treat it as an unusual contribution from a physicist trying to engage with their field.So, is this really a story of a bunch of stupid academics getting fooled?Maybe maybe not.Either way, I think that the hoax still exposes something really interesting about the way we recognize intelligence.One thing he had shown was that you could make nonsense sound intelligent, which is something I think that all of us kind of know intuitively.And that kind of got me wondering, what about the reverse?You know, how often does someone have a genuinely intelligent idea, but they explain it so badly that it sounds like nonsense?
And how are we supposed to know the difference?

2. The Curse of Knowledge Explained

The speaker reflects on struggling with Rawls and introduces the idea that experts often fail to explain things clearly. A tapping experiment shows how knowledge can make people overestimate how much others understand.

I've been thinking about this a lot because I've been reading John Rawls' A Theory of Justice for several months now, and I can safely say that this is the hardest book I have ever read.Uh there are pages in here I've gone through several times, and I have no idea what in the world he's talking about.And he was obviously an extremely intelligent person.So, my first assumption is that of course the problem is with me.But, I have to wonder, you know, after struggling with this book for so long, I can't help wonder how much of the complexity comes from the ideas themselves, and how much comes from the author just not being ableto explain them very well.Because as an educator, I know all too well that just because someone knows a subject really well, that doesn't mean that they're good at explaining it.
Steven Pinker writes about this problem in his book Sense of Style.He calls it the curse of knowledge, which is this idea that experts have difficulty imagining what it's like for someone else not to know something that they do in fact know.And so, they have a tendency to overestimate novices' understanding, and in the process, they skip important basic steps without really realizing it.There's a really simple experiment that illustrates this.It was conducted by a Stanford graduate student named Elizabeth Newton, and later became well-known through Chip and Dan Heath's book Made to Stick.So, in this study, one person was asked to choose a really easy and familiar song like Happy Birthday.And then all they had to do was tap out the rhythm on the table so that another person could listen to the tapping, and then just guess the song.Now, before they ran the experiment, they asked the tappers to make a prediction about how often the listeners would be able to recognize the song, and they guessed that the listeners would be able to get it right about
half the time.But it turns out that when they ran the experiment, they were only able to identify three out of 120 songs that were possible, which is only about 2.5%.So, the people tapping the song, they weren't able to put themselves in the listener's shoes, so to speak.Because as they tapped, they could hear the melody in their heads, and so to them at least, the answer seemed obvious.But of course, the listeners didn't have any melody in their head, and so all they really heard was this series of disconnected tapping sounds.And because the tappers weren't able to uh temporarily imagine what it was like not to know the song, they had a a very poor sense of how little information they were actually communicating.

3. How Expertise Changes Thinking

This section explains that expertise is often domain-specific and changes how people process information. Examples from chess and reading show how experts rely on automatic patterns that are hard to articulate.

And by the way, I should probably point out that when I say smart people, I'm mostly talking about people who have developed a lot of knowledge in a particular area, because intelligence by itself, it doesn't make someone anexpert in everything.You know, a person could be really good at mathematics, but know nothing about for example, fixing their car.So, this disconnected tends to happen when someone is working inside of a subject that's extremely familiar to them.And so, what happens is as people gain knowledge or you just get better at doing something, they begin to process information more as whole patterns rather than as separate individual parts.You can see a really good example of this when you compare beginner and expert chess players.Beginners tend to think about their game and their strategy on the level of individual pieces or individual moves.But experienced players, they see several pieces and several moves together as a familiar arrangement.
And so, this allows really strong chess players to remember positions that are taken from actual games much better than beginners, because they're grouping the pieces into meaningful patterns rather than trying to memorize every piece and every move individually.And it's no different with something like reading.With enough practice, smaller steps like decoding word parts or syntax or grammar, punctuation, all of that becomes automatic.But those automatic steps are also harder to explain precisely because they've become so automatic, because you're no longer thinking about them anymore.And so you sort of take for granted how foundational, but also they are.

4. When Complexity Hurts Credibility

The speaker shifts to the opposite problem: making good ideas sound worse by using unnecessary jargon. Experiments by Daniel Oppenheimer show that overly complex writing can make authors seem less intelligent.

Now, so far I've mostly been talking about experts who skip important steps without realizing it, but there is another way that smart people can end up sounding stupid.And that's when a person has a perfectly good idea, maybe even a brilliant idea, but then makes the language more complicated on purpose because they think, well, you know, that's what they need to do in order to betaken seriously.They need to dress it up in big words or technical jargon.That's the same assumption that Sokal exploited in his experiment.And what's funny about that is that doing that can sometimes have the opposite effect.Daniel Oppenheimer conducted a series of experiments where readers evaluated different pieces of writing.Some versions of this writing used unnecessarily long and complex language.But other versions had the exact same ideas only they were written more plainly using more basic vocabulary.
And what they found is that when those ideas were genuinely good ideas, the writers who used the more complicated language, they were judged to be less intelligent rather than more intelligent.

5. Writer Responsibility and Clear Style

The final section balances the need for reader effort with the writer's duty to communicate clearly. Using Adler, Van Doren, and the Faulkner-Hemingway exchange, it argues that deep ideas do not require complicated language.

Now, that doesn't mean that every difficult book is written poorly or that every idea can be reduced to a few simple sentences.I mean, some subjects require technical language and there's just no way around it.And some ideas take a really long time to understand because they really are complicated.So, certainly the reader has to show up.They have to put in the effort.But, the writer has some responsibility here, too.This relationship between the reader and the writer is expressed really well in Adler and Van Doran's How to Read a Book.So, to explain this, they use a baseball analogy.The writer is the pitcher, the writing is the ball, and the reader is the catcher.Now, of course, the catcher, or the reader in this case, they have to be active.They have to pay attention and make the effort to catch whatever writing is being thrown at them.
But, the pitcher, or the writer, still needs some control.If the ball is thrown 10 ft over the catcher's head, it doesn't matter how much effort the catcher makes, they're not going to be able to catch it.This also reminds me of a famous exchange between William Faulkner and Ernest Hemingway.Faulkner once criticized Hemingway by saying that Hemingway never used any words that made the reader need to consult a dictionary.And Hemingway is reported to have said, "Poor Faulkner, does he really think big emotions come from big words?He thinks I don't know the $10 words.I know them all right, but there are older and simpler and better words, and those are the ones I use."In fact, Hemingway's simple and clear writing style has been emulated perhaps more than any other American writer.And don't get me wrong, Faulkner was obviously a brilliant writer, too, and the complexity of his prose wasn't an accident, but I think Hemingway had a point.
You don't need complicated language to express something deep and meaningful.
Seek backward 5s ←
Longer seek (10s) Shift ←
Play Space Seek forward 5s →
Longer seek (10s) Shift →
0:00 Auto-scroll A Copy link at current time S

Why You Can't Explain What You Read