Writing This Blog With AI Help, Grounded in My Own Experience

I’m fairly open about this: a lot of posts on this blog start as a brainstorm with AI. But there’s a line I keep strict between “AI-assisted” and “AI-written,” and that line isn’t always easy to hold consistently — there are a few older posts on this blog that, reading them back now, clearly show I wasn’t careful enough about it.

What I actually do

I give the AI real context — technical decisions I actually made, problems I actually ran into, code that actually exists in this repo. AI helps me structure a first draft faster. But every fact, number, and conclusion in it gets checked against the actual code or my actual experience before it’s published. There was one time a draft included a specific number — something like a build-time reduction — that sounded plausible and fit the narrative I was building perfectly. When I checked, it turned out to be a number I’d never actually measured, just something that “sounded right” to the model. I cut it before publishing. That’s the kind of mistake that slips through easily if I only skim a draft instead of actually reading every claim in it.

Why this matters to me

If content is purely AI-generated without editorial oversight, two bad things happen. First, the quality gets generic — it could be anyone’s writing, because it’s missing the specific details only I would know. Second, this is also relevant to something concrete like AdSense approval — Google explicitly states that AI content without human oversight typically fails review, because it isn’t genuinely “high-quality, original, and attracts an audience.” I read this while preparing the blog to apply for AdSense, and it’s part of why I got more serious about this editorial process, not just as a matter of writing ethics.

How I keep my own voice

I always rewrite the opening and closing manually, because those are the parts that show how I actually think, not just how information gets organized. Specific details — project names, numbers I actually measured, why I chose A over B — get filled in by hand, because that’s what makes a post impossible for anyone but me to regenerate. An AI draft is a decent starting point for structure, but structure alone isn’t enough to make writing feel like there’s an actual person behind it.

AI is a tool that speeds up the process, not a replacement for experience. As long as I stay in control of what’s actually true and worth sharing, the result stays authentic — though honestly, I’m still figuring out exactly where the line sits between “assisted” and “too lazy to edit.”