You can understand a complicated algorithm and still have absolutely no idea what to say to a friend who's having a terrible day.
The temptation is to offer a solution. There are three things they could do. You've already ranked them.
They were hoping you would listen.
Situations like this make me suspicious of how casually we use the word smart. Someone gets good grades, solves difficult problems, or speaks confidently about something we don't understand, and the label sticks.
Then we quietly expect it to explain everything else about them.
Their judgment. Their self-awareness. Their ability to handle an argument without turning it into a courtroom drama.
That's a lot of responsibility for one adjective.
An inconvenient amount of life happens outside exam conditions
I understand the appeal of grades and scores. There's something comforting about a question with a correct answer and a clear way to check it.
Data science gives me plenty of that satisfaction. A calculation works. A script runs. I can inspect the result and figure out whether I've made progress.
Other situations are less cooperative.
How do you know when to challenge someone and when to give them space? When does persistence become stubbornness? How do you recognize that the plan you've spent weeks defending is solving the wrong problem?
There usually isn't an answer key. Occasionally, there's an awkward conversation several months later.
A grade tells me something about my performance on the work being assessed. The trouble starts when I ask it to describe my whole mind, or someone else's.
I wouldn't choose a person to help me navigate an unfamiliar city based on their ability to solve equations. I'd want someone who notices their surroundings, reads a map, and can admit when we've walked past the same bakery three times.
Different situation. Different abilities worth paying attention to.
That doesn't make academic ability unimportant. It makes the question more specific.
Smart at what, under which conditions?
Gardner gave me a wider vocabulary
Reading Howard Gardner's Frames of Mind gave me another way to approach that question.
Gardner proposed multiple intelligences: ways of understanding ability that extend beyond the kinds of reasoning usually associated with being academically gifted.
Some concern language and logical or mathematical reasoning. Others concern music, spatial thinking, or the skilled use of the body.
He also described interpersonal intelligence, involving an understanding of other people, and intrapersonal intelligence, involving an understanding of yourself.
What interested me was how much this made me notice.
A dancer can recognize and correct a mistake in a movement I can barely describe. A musician can hear a relationship between sounds that passes straight through my ears. A good storyteller can choose a small detail that changes how I understand an entire character.
I might recognize the result without understanding the work behind it.
That's an uncomfortable position for someone who likes to think they're observant.
I treat Gardner's categories as a useful lens, rather than a settled map of how the mind works. Finding a framework appealing doesn't establish every claim it makes.
But it did expose a habit of mine: giving extra weight to abilities I understood well enough to recognize.
Logical reasoning is familiar territory for me. So are the satisfactions of code and data. When someone does those things well, I can often explain why their work is good.
With other abilities, I'm more likely to say, “They're just naturally good at that.”
Which can be a convenient way of overlooking everything they've learned.
The problem changes while you're solving it
Consider a small data project.
Someone asks for a dashboard showing average response times. You clean the data, calculate the averages, and make the chart readable. Everything checks out.
Then you discover that the person using it needs to know which requests have been waiting so long that someone should intervene.
The average is correct. It just doesn't answer their question.
At that point, more skill with the plotting library won't help much. You need to ask what decision the dashboard is supposed to support, listen to the answer, and be willing to change what you've built.
The arithmetic still matters. So does recognizing when arithmetic isn't the current difficulty.
That's part of what makes intelligence interesting to me. Real problems rarely stay inside the boundaries of one ability.
You might need careful reasoning to investigate an error, clear language to explain it, and enough self-awareness to notice that you're dismissing a suggestion because it came from someone less experienced.
That last one is particularly annoying. It doesn't produce a helpful error message.
It also changes how I look at people whose strengths differ from mine. Someone who asks a simple question may be doing more for the project than someone producing a complicated answer.
“Why are we building this?” can be a technically useful contribution.
Especially when everyone else is already choosing libraries.
Understanding yourself can be surprisingly inconvenient
The part of Gardner's framework I keep returning to is intrapersonal intelligence.
Knowing yourself sounds pleasant. Reflective. Possibly something you do beside a window with a notebook.
In practice, it can involve admitting that you've spent half an hour researching a tool because starting the actual work makes you uncomfortable.
I've caught myself scrolling instead of writing, or imagining a future science fiction novel instead of working on what's in front of me.
The imagined novel is excellent, incidentally. It has the considerable advantage of never having been written.
I used to find it easy to describe this as a simple discipline problem. Sometimes that's a useful description. Sometimes it tells me very little.
What am I avoiding?
A task I haven't broken down properly? A decision I don't know how to make? The possibility that the first attempt will be worse than the version in my head?
Those questions give me something to work with.
If the task is vague, I can define the next step. If I don't understand something, I can identify what I need to learn. If I'm protecting an imaginary perfect result, I can write an imperfect paragraph and finally have something real to edit.
None of this means a productive afternoon proves intelligence, or a distracted one disproves it. Attention, energy, habits, and circumstances matter too.
But understanding my own behavior helps me use whatever ability I have.
It's difficult to work around a problem while insisting it doesn't exist.
Comparison needs a smaller question
There is a very efficient way to make yourself feel inadequate: compare your unfinished work with everyone else's most visible achievement.
Someone publishes a paper. Someone places well in a Kaggle competition. Someone writes a sentence so good that you briefly consider abandoning language altogether.
Dostoevsky is not especially helpful in this regard.
I admire these things. The problem begins when admiration turns into a vague judgment about my own intelligence.
“They understand this subject better than I do” is a specific observation. It might even be useful.
“They're smart, and I'm not” closes the investigation before I've learned anything.
What do they actually do better?
Perhaps they know the underlying mathematics. Perhaps they have more practice recognizing a particular kind of problem. Perhaps they explain their reasoning clearly enough that I can see gaps in my own understanding.
Now there is something I can study.
A specific gap gives me somewhere to start.
This doesn't require pretending that everyone has identical abilities, or that effort guarantees the same result for everyone. It just means a broad label is often less useful than a precise question.
I'd rather find out what I'm missing than spend the evening deciding what kind of person that makes me.
And some things I enjoy don't need to become competitions at all.
I can love literature without becoming a great novelist. I can spend time thinking about human behavior without producing an impressive theory of it. Curiosity is allowed to have interests that look unremarkable on a résumé.
Leaving room to be wrong
I still value people who can solve difficult problems. I still want to get better at the technical work I care about.
But I'm increasingly interested in what happens when someone's knowledge runs out.
Do they notice? Can they ask a useful question? Can they change their mind without treating it as a personal defeat?
Those are qualities I want to practice, partly because I know how tempting it is to protect the feeling of being competent. You can spend a surprising amount of energy defending an answer that a small correction would improve.
Maybe that's why I keep coming back to the friend having a terrible day.
I can prepare an explanation, identify patterns, and offer a sensible plan. I might even be right about parts of it.
But first, I need to find out what they're trying to tell me.
The answer can wait.