I have written a lot of posts.
Reflections, mostly.
What I learned this week, what I noticed about AI, what fatherhood taught me about focus.
Some did fine. Most didn’t.
I kept asking why.
The writing wasn’t bad.
The thinking wasn’t shallow.
So what was missing?
The Uncomfortable Answer
Right now, AI is the only thing anyone wants to hear about.
Not my opinion on it.
Not my nostalgia about how things used to be built.
People want the latest.
What actually happened, what actually broke, what actually shipped.
Opinions need authority to travel.
Nobody owes a stranger’s opinion their attention, especially not in a feed already full of AI takes.
Proof works differently.
Proof Doesn’t Ask Permission
A working demo does not need your job title.
A real transcript of an AI agent failing and you fixing it does not need your follower count.
Code that runs, numbers that add up, a screenshot of the actual output.
These things carry their own weight.
Nobody has to trust you first.
They can just look.
I am a developer, not a public figure.
I don’t have a divorce settlement to write about, or a celebrity account to lean on.
What I have is things I built.
Why This Matters More Now
Every developer I know wants to write.
Wants to build something people recognize them for.
Most quietly give up after a few posts that go nowhere.
They assume the problem is the writing.
Usually it is the genre.
A reflection asks the reader to trust your judgment first.
A teardown asks the reader to trust their own eyes.
One requires you to have already earned attention.
The other earns it in the same post.
What This Looks Like in Practice
Not “here is what I think about AI agents.”
Instead, “here is the agent, here is what I asked it to do, here is exactly where it broke, here is what I changed.”
Not “here is my philosophy on shipping fast.”
Instead, “here is the project, here is the commit history, here is the thing that is actually live right now.”
The claim disappears.
Only the evidence remains.
This is harder to write.
You cannot hide behind a good sentence.
The work has to actually exist before the post does.
The Shift I’m Making
I am not stopping reflections completely.
But they are not the front door anymore.
The front door is proof.
Something built, something broken and rebuilt, something a reader can verify without knowing who I am.
If I want a new client or a new job to find this writing useful, this is the only version of my writing that does that job.
Not the version that asks to be believed.
The version that shows.
One Line to Keep
You don’t need a title to publish proof.
You only need something you actually did.
That part, at least, is fully in my control.
Leave a Reply