Writing to Understand

I used to think you needed to be an expert before you could write about something. That writing was the output of understanding. First you learn, then you explain.

I had it backwards.

The blank page as a debugging tool

The moment I try to explain something in writing, I discover the gaps. The parts I thought I understood but actually just had a vague feeling about. The connections I assumed existed but can’t articulate.

Writing is not the output of thinking. Writing is thinking.

This is why rubber duck debugging works. It’s why teaching is the best way to learn. The act of translating an idea from the fuzzy space in your head into concrete words forces precision.

The draft as exploration

My best technical posts started as confusion. I’d encounter something I didn’t fully understand, and instead of bookmarking it for later, I’d open a blank document and start writing.

Not writing about it — writing through it. Following the thread wherever it led, asking questions on the page, trying different explanations until one clicked.

Half of these drafts never become posts. That’s fine. The draft served its purpose.

Permission to be wrong

The hardest part is giving yourself permission to write something that might be wrong. Or incomplete. Or obvious to someone with more experience.

But here’s the thing: writing that comes from genuine curiosity is almost always interesting, even when it’s imperfect. Readers can tell the difference between someone exploring an idea honestly and someone performing expertise.

I’d rather read a thoughtful wrong take than a polished summary of conventional wisdom.

So I keep writing. Not because I have answers, but because writing is how I find them.