In 1927, Ernest Hemingway published a short story called Hills Like White Elephants. It takes place at a train station in Spain. A man and a woman are sitting at a table, drinking beer, waiting for a train to Madrid. They talk about the hills in the distance, about drinks, about whether to order another round. They talk about a "simple operation." They never say what the operation is.
The story is roughly 1,500 words. Almost nothing happens. Nobody enters or leaves. Nobody throws a punch or slams a door. Two people sit at a table and talk past each other, and by the time you reach the final line, you understand everything about who they are, what they want, and what's about to happen to them. You understand who holds the power and who is afraid. You understand that this couple is probably finished, even though neither of them says so.
What gets me is how little Hemingway gives you. There are no interior monologues. No narrator stepping in to tell you how the woman feels when the man says "It's really an awfully simple operation." You just hear what they say, and you feel the weight of what they don't.
If you're trying to learn how to write dialogue in fiction, that story is the whole syllabus. Dialogue works when it carries more than the words on the page. When two characters talk, the interesting part is almost never the thing they're actually saying. It's the gap between what they mean and what comes out of their mouths.
Most writing advice treats dialogue like a skill you bolt onto a scene. Add some quotation marks, make it sound natural, keep it snappy. But the writers who do it best treat dialogue as the place where characters reveal themselves by trying not to.
Subtext is what the character can't say out loud
In Hills Like White Elephants, the word "abortion" never appears. Never. And yet every single line either pushes toward that reality or pulls away from it. The man keeps saying how simple the operation is. The woman keeps changing the subject, looking at the hills, asking about drinks. The word hangs over the whole story like weather.
This is what good dialogue actually does. People don't say what they mean. They circle what they mean while talking about something else entirely. The man in Hemingway's story isn't really talking about a medical procedure. He's negotiating for his freedom. The woman isn't really asking about the hills. She's trying to find a reason to stay.
Elmore Leonard understood this instinct as well as anyone. His famous advice was that if you can skip a line of dialogue without losing anything, you should skip it. But the corollary matters more: what you can't skip is the distance between what a character wants and what they're willing to say out loud. That distance is where all the tension lives. You don't need to name it. You just need to let the reader feel it.
Real dialogue sounds like people, not like information
George Saunders talks about this in A Swim in a Pond in the Rain. The way people actually talk is messy. Full of interruptions and half-finished thoughts, answers to questions nobody asked, sudden pivots into something unrelated. We repeat ourselves. We trail off. We say "anyway" and change the subject when we get too close to something we don't want to feel.
Saunders uses the word "load" to describe what good dialogue carries. It's the weight of everything the character isn't saying, pressed into the shape of what they are saying. A character who responds to "Do you love me?" with "Did you feed the dog?" is telling you everything. The line itself is almost nothing. The load is everything.
I think the quickest test for dialogue is also the simplest one. Read it out loud. Actually say the words. If you'd never say a line like that to a friend at a coffee shop, your character probably shouldn't say it either. This doesn't mean dialogue has to be realistic in a transcription sense. Nobody wants to read actual conversation with all its "ums" and dead ends. But it has to feel like it could come out of a human mouth.