I published three articles this week. I didn't sit down to write any of them.

They came from a work session. I was building an email triage system — reorganizing labels, writing classification logic, wiring up a cron job. Somewhere in the middle of that, I said a sentence that landed: "Email isn't hard because of volume. It's hard because of ambiguity."

That became an article. The system I built became another. The pattern I discovered — controlling AI automations with plain markdown files — became a third.

I didn't plan content day. I did the work. The content was already in it.

The Old Way

Most content advice starts with "what should I post about?" You brainstorm topics, outline posts, block time to write. You stare at a blank page and try to be interesting on command.

That works for some people. It never worked for me. Forced content reads like forced content. The audience can tell.

The Work Is the Content

Every real work session has moments worth sharing. A problem you solved. A sentence that crystallized something you've been thinking about. A pattern you noticed that others haven't named yet.

The issue was never a lack of things to say. It was that those moments happened while your hands were busy, and by the time you sat down to "create content," the energy was gone.

How I Capture It Now

When I'm working with Claude Code, every session is a conversation. I'm building, debugging, designing — and talking through decisions as I go. When something lands, I notice it.

"That's an article."

"That's a standalone post."

"That line is worth saving."

I say it out loud. We draft it right there, in the same session, while the thinking is still warm. It goes into a drafts folder. I review and publish later.

The drafting takes two minutes. The insight took two hours of real work to earn. That's the ratio that makes content authentic — you're not manufacturing ideas, you're documenting them.

Why It Works

Content created from real work has something that planned content doesn't: specificity. You're not writing about "email productivity tips." You're writing about the exact system you built, the exact problem it solved, and the exact sentence that fell out of your mouth while you were elbow-deep in code.

Readers can feel the difference between someone who researched a topic and someone who lived it. The details are different. The confidence is different. The usefulness is different.

The System

I keep a drafts folder that syncs between my server and my laptop. When a moment hits during a work session, we draft it immediately. The draft sits until I'm ready to review, edit, and publish.

No content calendar. No brainstorming sessions. No blank pages.

Just work, with a habit of noticing when the work says something worth sharing.

The Shift

Stop asking "what should I post about?" Start asking "what did I just do that someone else would want to know?"

The answer is almost always sitting in your last work session. You just have to catch it before it cools off.