How these blogs actually get written
The voice you read in these posts is mine. The typing is not. Here's how that actually works, because I think it matters and I keep getting asked.
I rant. Often.
Anyone who knows me knows the pattern. I get an idea. I rant. The rant has the actual thinking in it. Three or four threads tangled together, half of them more interesting than the headline I started with. By the time I'm done talking, I've been over the topic from five angles and the structure already exists. It's just not on a page yet.
That used to be where the bottleneck was. The thinking was done. Sitting down to write 800 coherent words about it took me hours I didn't have. Most of the ideas died on the rant. They never made it past the in-my-head version.
What my AI knows about how I sound
A while back I ran my whole sent-email folder through a voice check. Years of how I write to clients, friends, vendors, lawyers. How my sentences flow. Words I reach for. Words I never use. The beat I hit when I care about something versus when I'm just being polite.
That profile lives in my agent's context. When I hand it a rant, it doesn't have to guess at my voice. It's already got it. The output isn't generic AI prose. It reads like an email I would actually send. Because the model behind it has read thousands of those.
What actually happens between idea and post
The loop is simple.
I rant. Sometimes out loud and I get it transcribed. Sometimes as a brain dump in a message. Sometimes as messy notes I send to myself. The format does not matter. The agent just needs the thinking and the angle.
The agent turns the rant into a draft post. Same ideas. My structure. My word choices. The post lives on web-dev first. Never prod yet. The web-dev domain is locked to my home IP, so nobody else sees the draft.
I read it end to end. I make changes. Some are one sentence. Some are half a paragraph. That happens when the angle is off. Sometimes the agent puts words in my mouth. Words I would never say. I cut those. If a part reads like a bot wrote it, it gets killed.
If I like it, I push from web-dev to prod. If I don't like it, I scrap the whole post.
That last part matters. Not every rant deserves to be a blog post. Sometimes the ideas don't hold up once they're on the page. The post never makes it out.
Some people will call this cheating
Some people will look at this and say it's AI slop. I disagree. The ideas are mine. The reasoning is mine. The voice was scraped from years of me actually writing in my own voice. Every post is read end to end and edited before it ships. Posts that don't work get killed instead of polished into something I don't believe.
What changed is the friction between idea and published thought. That used to be a four-hour wall I would not climb on a busy week. Now it's a thirty-minute review. The wall moved. The thinking didn't.
Writing in public was never about proving I can type. It was about getting ideas out. Holding it all in my head, in the time I had, cost me ideas. This system stopped that.
Why I think this is the right shape
If you know me, yeah, I get too excited. Yeah, I rant hard. It's hard for me to fit all I want to say into one clean paragraph. The system helps with that. The system does not replace me. It clears the path from what I want to say to the page.
That's it. If you build AI tools for a job, you should use AI for the boring work too. If not, we don't live by what we sell.
← Back to blog