Featured entry

Writing as debugging

When I can't explain a concept plainly, I usually don't understand it yet. Writing is how I find the missing piece.

Communication • craft

I used to think writing was about communication.

Now I think it’s mostly about debugging.

The moment I realized

I was stuck on a technical problem for two days.

I had tried everything:

  • Different approaches
  • More research
  • Talking to colleagues
  • Taking breaks

Nothing clicked.

So I started writing about it.

Not for anyone else.
Just for me.

The process

I wrote:

  • What I was trying to build
  • What I expected to happen
  • What was actually happening
  • Where I thought the disconnect was

I didn’t try to sound smart.

I just tried to be clear.

The breakthrough

Halfway through writing, I found it.

It was a simple assumption I’d been making.

An assumption that was wrong.

Once I wrote it down, I couldn’t unsee it.

The solution became obvious.

I had debugged the problem with words.

Why writing is debugging

1. It forces clarity

When you write, you can’t rely on vague mental models.

You have to explain things step by step.

That process exposes gaps in your thinking.

2. It slows you down

Technical problems often feel urgent.

Writing forces you to pause.

In that pause, you see things you missed when you were rushing.

3. It externalizes your brain

Your brain is messy.

Writing makes it linear.

Linear thinking reveals logical errors.

4. It creates a record

When you come back to a problem later, you have notes.

But more importantly, you have the process of how you solved it.

Writing as a daily practice

I started doing this regularly:

  • Write about problems I’m stuck on
  • Write about concepts I’m learning
  • Write about systems I’m building

It didn’t always lead to immediate breakthroughs.

But it always made me better.

The shift in perspective

I used to think: “I’ll write about this once I understand it.”

Now I think: “I’ll understand this once I write about it.”

That shift changed everything.

Writing as a tool, not a chore

Writing isn’t just for blogs or documentation.

It’s a tool for thinking.

It’s a way to debug your own mind.

When you’re stuck:

  • Don’t just search for answers
  • Write down the problem
  • Explain it like you’re teaching someone
  • See where your explanation breaks

That’s often where the solution is hiding.

A simpler approach to learning

I’m not trying to write the perfect article.

I’m just trying to understand something more clearly.

If I can explain it simply, I probably understand it.

If I can’t, I need to keep writing.

The debugging mindset

Writing is debugging.

Debugging is writing.

Both are about:

  • Observation
  • Hypothesis
  • Testing
  • Iteration
  • Clarity

Once you see it that way, writing stops feeling like a chore.

It starts feeling like a superpower.