Writing It Down Was How I Understood It

I started writing about this work thinking of it as something separate from the work itself — a way to share what I had learned, afterward, once the learning was already done. The writing, in this picture, was a record. A report filed after the fact. I was wrong about the order, and the mistake turned out to be a revealing one. The writing was not, most of the time, a record of understanding I already possessed. It was, over and over, how I actually arrived at the understanding in the first place.

This is the lesson behind the lessons, in a way — the reason this whole record exists at all. So it feels right to spend one entry on it directly, near the end.

You cannot write clearly what you do not understand

The core discovery was simple and humbling: trying to explain something forces a kind of clarity that thinking alone never quite does. You can hold a fuzzy, half-formed sense of something in your head — a comfortable feeling of I get this — and that feeling can persist indefinitely, completely unchallenged, as long as you never have to make it precise. Thinking is forgiving. It lets you skate over the parts you have not actually worked out.

Writing is not forgiving. The moment you try to put the thing down in clear words, the fuzziness becomes undeniable. The blank page is an honest and merciless examiner of what you actually know, because clear prose has no room for the hand-waves and the and then it sort of works that your private thoughts tolerate so happily. You cannot write a clear sentence around a hole in your understanding. The sentence simply refuses to form.

Writing exposes the gaps you did not know were there

Again and again, I would sit down to explain something I was certain I understood, and I would hit a point where the explanation just would not come. Where I reached for the next sentence and found nothing solid to stand on — because, it turned out, I had been quietly relying on a leap I had never noticed I was making. The understanding I had felt so confident about had a gap in it, and the gap had been completely invisible to me right up until the writing dragged it into the light.

This happened far too often to be an accident. The places where the words would not come were, with eerie reliability, exactly the places where I did not actually know the thing I thought I knew. Writing was not adding the gaps. It was revealing gaps that had been there the whole time, hidden underneath the warm and unjustified feeling of comprehension.

Writing is a debugger for your own thinking

So writing quietly became one of my most valuable tools — not for communication, but for finding the bugs in my own understanding, in very much the same way that running code finds the bugs in your logic. A thought can remain vague and subtly broken inside your head forever; nothing forces the break to surface. Compile it into clear prose, though, and the breaks become visible immediately, because the prose will not run, so to speak, around them.

I came, eventually, to write not primarily to communicate what I knew, but to discover what I did not. Sitting down to explain a thing became a diagnostic act: if the explanation flowed, my understanding was probably real; if it stalled and tangled and refused to cohere, that was a precise signal pointing at the part I had not actually worked out. The struggle to write was the struggle to think, made visible and externalized where I could finally see it.

The discipline imposed by a reader

Writing for someone else adds a second force on top of the first, and it is a powerful one. When you write for a reader, you cannot lean on your own private context — the shorthand, the unstated assumptions, the you know what I mean that lets your internal understanding feel seamless and complete. A reader does not have your context. A reader has only the words on the page.

Which means you have to actually supply the reasoning, all of it, in the open, where its absence would be obvious. And the act of supplying it forces you to check whether the reasoning is genuinely there or whether you had merely been assuming it. Explaining something to an imagined other person is, in the end, a way of catching yourself — of noticing the steps you skip when you are only talking to yourself, because you are too kind an audience to demand them.

Understanding you cannot explain is not understanding

All of this hardened into a belief I now hold fairly firmly: if I cannot explain something clearly, I do not actually understand it, no matter how strongly it feels like I do. The feeling of understanding and the ability to explain are two genuinely different things, and the gap between them is precisely where most of my false confidence had been quietly living all along.

This makes the explanation a test, and it makes failing that test useful rather than embarrassing. When I cannot write a thing clearly, that is not a writing problem to be pushed through with better phrasing. It is a thinking problem, a sign that the understanding underneath is not yet real, and the right response is to go back to the understanding, not to the words. The words were only ever the instrument that detected the deficiency.

Why share it, and not merely write it

Writing privately gets you most of these benefits, and for a long time that would have been reason enough. But sharing the writing — exposing the explanation to people who might disagree, who do not hold your assumptions, who will notice the hand-wave you managed to slip past yourself — sharpens it further still. An audience that can push back is a stronger examiner than an imagined one.

And there is a second reason, the one this entire project ultimately rests on. The honest account of a messy, failure-strewn process is, I have come to believe, close to the most useful thing one person can hand another who is walking the same hard road. Not the polished result, which mostly intimidates. The actual process, with the confusion and the dead ends left in. So the sharing is not just a sharper way to think. It is the small act of leaving a real map for whoever comes next, drawn by someone who got lost in exactly the places they are about to.

The deeper lesson: explaining is thinking, not reporting

What it comes down to is that I had the fundamental relationship backwards. I had assumed you understand first and write second — that writing is reporting, the transcription of a thought already complete. For genuinely hard things, this is simply false. Writing is not the report that comes after the thinking. It is, to a degree I never expected, a large part of the thinking itself.

The clarity does not exist first and then get written down. The clarity is produced by the struggle to find the words — it is manufactured in the act of writing, not merely recorded by it. Once I understood that, I stopped treating writing as overhead, as the tax you pay after the real work is done, and started treating it as one of the most powerful thinking tools I had ever stumbled into. This record was never just documentation of the journey. Writing it was part of how the journey actually happened.

— No signals, no returns, not investment advice.