I'm Not Writing This For You

I'll be honest with you about something.

When I sit down to write one of these posts, I'm not really thinking about you. I'm not thinking about search rankings, or what's going to perform well on LinkedIn, or whether this is the kind of content my audience wants. I'm thinking about something that's been rattling around in my head for a few days, and I need to get it out so I can actually understand what I think about it.

The blog is a thinking tool. The fact that you can read it is almost incidental.

Writing as a forcing function

There's a thing that happens when you write something down properly. Not notes. Not bullet points. Actual sentences, actual paragraphs, a point of view with a beginning and an end. The half-formed thing that felt so clear in your head reveals itself as considerably less clear than you thought.

Every time I write a post — even a short one — I find myself reaching a paragraph where I have to either commit to a position or admit that I don't actually have one yet. That moment of friction is the whole point. It's not a problem to solve. It's the work.

If I can't write it, I don't understand it. That's a useful thing to find out.

The pipeline

Here's what actually happens to an idea in my world.

It starts as a thing I'm thinking about. Usually while walking, sometimes while editing photos, occasionally while playing a set and my brain has eight bars of nothing to do. An observation, a question, a disagreement with something I read. It gets added to a note on my phone.

Then it sits there for a while. Most of them stay there forever.

The ones that survive become a blog post. Not because I've decided the world needs to hear my thoughts on the Lumix S9 or whether street photography is actually that hard — but because writing it forces me to pressure-test the idea. By the end of a post, I either believe it more or I've dismantled it entirely. Both outcomes are useful.

The ones that survive that become YouTube scripts. And this is where the writing really pays off. A good blog post is essentially a first draft of a video. The structure's there, the argument's there, the transitions are implicit. I'm not sitting in front of a camera trying to remember what I wanted to say — I'm delivering something I've already thought through.

The ones that make it all the way become presentations. Keynotes, talks, the occasional panel. Same idea, different container. By the time something reaches a slide deck, I've usually said it in three different formats and I actually know what I'm talking about.

Where AI fits into this

This is the part people probably want to know about, given that this whole site was built with Claude.

I want to be precise about it because I think there's a muddled conversation happening about AI and writing. The concern is usually "is it authentic if AI helped?" But that framing misses what's actually interesting.

I use AI the way I'd use a smart colleague who's read everything and never gets tired. I'll share a half-formed idea and ask: does this hold up? What am I missing? What's the strongest version of the argument I'm not making? The thinking is mine. The AI is the friction.

What it's genuinely changed is the speed at which an idea can move through the pipeline. A thought on a walk becomes a blog post in an hour, a YouTube outline in another twenty minutes. The bottleneck used to be production. Now the bottleneck is having good ideas in the first place — which, honestly, is where the bottleneck should be.

That feels right to me.

The bit where I admit this post is an example

I started writing this because I was trying to work out why I'd built a blog when I'm not sure I have enough to say to justify one. I wanted to understand my own thinking about it.

I got about halfway through and realised I'd answered the question. The blog exists because the writing is the thinking, not the output. Whether anyone reads this particular post doesn't really change whether it was worth writing.

You reading it is a nice bonus, though.

---

If any of this resonates — the idea pipeline, using AI as a thinking partner, anything — I'd genuinely be curious to hear how other people work through ideas. Drop me a message.