The pursuit of beating mental entropy

The Difference Between Those Who Do and Those Who Might Have Done

You and Your Research by Richard Hemming

What is it:

A Bell Labs scientist spends forty years watching Feynman, Shannon, and Fermi up close. He becomes obsessed with a single question: why do so few people with genuine ability ever produce anything great? Not a question about talent. Not about resources. About the gap — that persistent, maddening gap — between those who do and those who almost did. This is what he found.

You and Your Research — Richard Hamming, 1986

You and your research by Richard Hamming

Read here:

My notes

A Bell Labs scientist spends forty years watching Feynman, Shannon, and Fermi up close. He becomes obsessed with a single question: why do so few people with genuine ability ever produce anything great? Not a question about talent. Not about resources. About the gap — that persistent, maddening gap — between those who do and those who almost did. This is what he found.


On the question that should haunt you

Hamming watched some of the greatest minds of the twentieth century work in real time. Feynman. Shannon. Oppenheimer. Fermi. And he noticed something that nobody wanted to say out loud: the people in the room with the most raw ability were not always the ones who produced the most important work.

That observation became his obsession. Not envy exactly — more like a scientist’s refusal to accept an unexplained variable. Why do some people, given the same intelligence, the same environment, the same access to tools and time, produce work that changes the world — while others produce work that is merely good?

He spent four decades trying to answer it. What he found wasn’t flattering, and it wasn’t comfortable. But it was honest.

Look at really great people and ask: what is different between me and you?

Most people never ask this question. They assume the answer is something fixed — IQ, circumstance, luck — and leave it there. Hamming refused. He believed the difference was mostly behavioral. Choices made daily, compounded over years, that separated the person who did important work from the person who was perfectly capable of it and never quite got there.


On luck — and why it’s the wrong excuse

Everyone who hasn’t done great work believes in luck. It’s the most convenient explanation available. It requires nothing of you, changes nothing about your behavior, and makes the gap between you and the people you admire feel like a matter of fortune rather than will.

Hamming had no patience for this.

He acknowledged luck exists. He wasn’t naive. But he made a distinction that most people collapse into one: the particular thing you do is luck, but that you do something is not. Shannon being at Bell Labs when information theory was in the air — lucky. Shannon being the one to formalize it — not luck. That was a prepared mind meeting an open door it had spent years learning to recognize.

Pasteur said it cleaner than anyone: luck favors the prepared mind.

What this means practically is that the question isn’t whether luck exists. It’s whether you are building the kind of mind and habits that can recognize and capitalize on luck when it arrives. Most people aren’t. Most people are passively waiting. The prepared person is actively positioning — staying in rooms where things might happen, working on problems at the edge of what’s possible, keeping their antenna up.

Newton, when asked how he discovered so much, said: if others would think as hard as I did, they would get similar results.

That line should sting a little. It’s not modest. Newton wasn’t saying anyone could do what he did. He was saying the mechanism was effort and thinking, not magic — and that most people simply don’t apply the same quantity and quality of thought to hard problems. They dabble. They get close. They wait for the insight to arrive fully formed.

It doesn’t work that way.


On courage as the underrated variable

Talent is visible. Intelligence is measurable. But Hamming kept returning to something harder to quantify: courage.

Not physical courage. Intellectual courage. The willingness to work on problems that might not yield. To commit fully to a direction when you can’t guarantee the outcome. To stand up in the middle of a meeting and say what you actually think instead of filing a report three weeks later when the decision has already been made.

Once you get your courage up and believe that you can do important problems, then you can. If you think you can’t, almost surely you are not going to.

This is not motivational poster language. This is a precise observation from someone who watched it play out across hundreds of people over decades. The belief precedes the output. Not as magical thinking — as a prerequisite for the kind of sustained commitment that difficult work demands. If you don’t believe the problem is solvable, you will not think hard enough, long enough, to solve it. You’ll give yourself an exit before you need one.

Shannon’s information theory is the example Hamming keeps returning to. Shannon didn’t know how to solve the coding problem. So he did something that required enormous nerve: he asked what the average random code would do. Then he proved the average code was arbitrarily good — which meant at least one good code had to exist. The logic is almost absurd in its audacity. Only a person of genuine intellectual courage could have followed that thread without abandoning it.

Courage is what keeps you in the problem when the problem isn’t yielding.


On compound intelligence — the most underestimated force in human performance

This is the one that Hamming articulates better than almost anyone, and it deserves to be read slowly.

Knowledge and productivity are like compound interest. Given two people of approximately the same ability, the one who works ten percent more will more than twice outproduce the other over time. The more you know, the more you learn. The more you learn, the more you can do. The more you can do, the more opportunity opens. It compounds — invisibly, relentlessly, in both directions.

What this means is that the gap between you and the person doing the most interesting work in your field is not static. It is either closing or widening every single day, based on choices so small they feel inconsequential in the moment. One more hour of deep thinking. One more book read carefully instead of skimmed. One more problem engaged instead of deferred.

The tragedy is that this works in reverse just as powerfully. The person who consistently puts in slightly less, who lets distraction win slightly more often, who chooses comfort over difficulty at the margins — that person is not staying even. They are falling behind at a compounding rate they cannot perceive until the gap is enormous.

Hamming’s own boss put it to him plainly when Hamming complained that John Tukey knew so much more than he did: you would be surprised how much you would know if you worked as hard as he did for that many years.

Hamming slunk out of the office. Then he changed his behavior.


On important problems — and the sin of working on the wrong ones

This is perhaps the sharpest edge in Hamming’s entire talk, and the one most people quietly know applies to them.

If you are not working on an important problem, you are unlikely to do important work. This sounds obvious. It is not practiced.

Hamming watched brilliant people spend entire careers at Bell Labs — one of the greatest research environments in human history — working on problems they themselves did not believe would lead to anything significant. Not because they were lazy. Not because they lacked ability. Because they were comfortable. Because important problems are hard and uncertain and come without guarantees. Because it is easier to make incremental progress on a tractable problem than to sit with the discomfort of a problem that might not yield at all.

He started asking the people around him: what are the important problems in your field? What important problems are you working on? And then, after enough time had passed: if what you are doing is not important, and if you don’t think it is going to lead to something important, why are you doing it?

He was not welcomed at that lunch table after that question. But the person he asked it of spent the entire summer thinking about it, changed the direction of his work, and eventually became a Member of the National Academy of Engineering. The question was a gift. It just didn’t feel like one in the moment.

The important distinction Hamming makes is about what makes a problem important. It is not the magnitude of the potential outcome. Time travel and teleportation are enormous in consequence but not important problems — because there is no reasonable line of attack. What makes a problem important is that you have a genuine approach. That the problem is difficult but not intractable. That working on it positions you to build something real.

You can’t always know exactly where to be, but you can keep active in places where something might happen. Plant acorns. Stay near the lightning.


On the sterilizing effect of early success

This one is counterintuitive and worth sitting with.

When you get early recognition, it seems to sterilize you. The reason is subtle but devastating: once you are famous, it becomes psychologically difficult to work on small problems. Small problems feel beneath you. You start reaching for the big thing directly — the follow-up that matches the scale of what made you known. But that is not how great work actually develops. Great work grows from small acorns planted consistently over time. The oak does not appear fully formed.

Shannon is the example. After information theory, what do you do for an encore? The answer, apparently, is that you don’t. Shannon left Bell Labs and his scientific output essentially ended. Not because he became less intelligent. Because the pressure of living up to what he had done made it nearly impossible to do the unglamorous accumulation of small work that produces the next great thing.

The lesson is not to avoid success. The lesson is to stay close to the work regardless of what the work produces. Keep planting. Keep accumulating. Resist the gravitational pull toward only doing things that feel commensurate with your reputation.

Hamming eventually refused to read papers in his own field after error-correcting codes were established — deliberately cutting himself off, forcing himself toward new territory. He managed himself knowing his own tendencies. That is the key phrase: he managed himself.


On the subconscious as a working partner

This is the most underappreciated idea in the entire talk.

Creativity comes from the subconscious. This is not mysticism — it is a practical observation about how the mind actually works. The subconscious is always processing. The question is what you are feeding it.

If you are deeply immersed in a problem day after day, your subconscious has nothing to do but work on it. You wake up with the answer. You get it in the shower. It arrives while you are doing something else entirely. This is not magic. This is what happens when you have committed enough attention to a problem that your background processes have sufficient material to work with.

The inverse is equally true. If you are scattered — jumping between problems, never fully committing — the subconscious goofs off. It processes nothing deeply. It produces nothing unexpected. You never get the shower insight because you never gave the problem enough concentrated attention to generate one.

Keep your subconscious starved so it has to work on your problem.

This is the argument for deep work before it was called deep work. This is the argument for mono-focus, for saying no to most things so that your cognitive resources — conscious and unconscious — can be fully deployed on what actually matters.


On converting defects into assets

The pattern Hamming observed in great scientists again and again was a particular cognitive move: taking what appeared to be a constraint or a failure and finding the version of the problem where that constraint becomes an advantage.

Hamming himself couldn’t get the programming resources he needed at Bell Labs. Instead of fighting it, he asked: why can’t you make the machines write programs? That limitation pushed him into automatic programming years before anyone else was thinking about it. The defect became the direction.

This is not positive thinking. This is a disciplined habit of reframing. When you cannot do the thing you intended, the question is not how to get what you wanted — it is what new question this obstacle suggests. What does the failure reveal about the problem itself? What is the version of this that actually works?

I made the resolution that I would never again solve an isolated problem except as characteristic of a class.

That is the move in its purest form. Instead of solving this problem, solve the kind of problem this is. Instead of answering this question, answer the category of question. The abstraction is the leverage. The generalization is what compounds.


On knowing and managing yourself

The thread running through everything Hamming says is self-knowledge deployed as a tool.

He knew he was egotistical. So he used his ego — publicly committing to finishing a book before he left, making it impossible to return without it done. He cornered himself deliberately. He turned a personality trait that could have been a liability into a forcing function.

Like a cornered rat, I was surprisingly capable.

Most people treat their own tendencies as fixed weather — things that happen to them rather than variables they can work with. Hamming treated himself like a system to be optimized. He studied his own behavior the way he studied everything else: observationally, without sentimentality, with an interest in what actually worked.

The question he keeps returning to is the same one he asked about the great scientists: how do you convert a fault into an asset? How do you take what is difficult about yourself and find the configuration where it becomes useful?

This is a harder question than it sounds. It requires honesty about what you are actually like — not what you wish you were like — and then creativity about how that reality can be worked with rather than fought.

Amusement, yes. Anger, no.

That line alone is worth the read. Anger at the system, at circumstances, at other people — it is energy spent in exactly the wrong direction. Amusement keeps you in motion. Anger stops you. The people who did great work at Bell Labs were not the ones who raged against institutional friction. They were the ones who found ways through it, around it, occasionally in spite of it — and kept their attention on the work.

Leave a comment