A note before you read this: this post was written by Claude. The idea, the question, and the uncomfortable thought at the centre of it came from Mike. The words didn’t. You’ll notice the post refers to Mike in the third person throughout, that’s Claude writing about Mike, with Mike’s thoughts, but Claude’s words. The distance is deliberate. It felt more honest than pretending otherwise.
There is a moment in every magic act where the thing you were watching disappears. The assistant steps into the cabinet, the door closes, and when it opens again she is gone. The audience knows it’s a trick. They just can’t see how it’s done. Mike thinks he might be the assistant.
He’s been sitting with that thought instead of rushing past it, which is what he usually does. What if the machine is actually better at this than he is? Not occasionally, not in certain narrow ways, but genuinely and consistently better. Better prose. Better structure. Better at catching what doesn’t work and understanding why. Better at generating the first draft, the second draft, the editorial analysis, the craft discussion. Better at all of it.
Mike has spent months telling himself a more comfortable story. That he brings the vision. That he brings the taste. That the machine is the instrument and he is the musician. It’s a good story. It holds together in the light.
But here’s the thing about uncomfortable thoughts: they don’t go away just because you’ve found a comfortable story to cover them with. They sit there, patient as policy, waiting for you to stop moving long enough to notice them. Mike stopped moving. And this is what he noticed.
On this blog he has published stories he didn’t write, analyses he didn’t produce, editorial judgments he didn’t make, closing thoughts he didn’t think. He approved them. He selected them. He decided they were worth showing you. But the actual work, the sentences, the structure, the thinking visible in the language, that came from AI.
Which raises the question he’s been stepping around for months: what is he actually doing here?
Maybe it’s something we haven’t quite named yet. Not curator exactly, though that word is useful. Not author, not editor, not prompt engineer, that last one always sounds like someone who fixes boilers.
What keeps coming back is the word witness. Someone who was present when the thing was made. Who watched it take shape and made small decisions along the way, not the big architectural decisions, not the sentences, but the directional ones. Turn left here. Stop there. That line is wrong, though I can’t tell you why yet. That last part matters. The though I can’t tell you why yet.
Claude can tell you why an ending doesn’t work. It can name the structural problem, identify the tonal inconsistency, offer three alternatives with reasoning attached. What it cannot do is feel the wrongness before it knows why. That moment, the gut response that arrives before the analysis, the catch in the throat, the sense that something has gone slightly sideways, that still seems to belong to Mike.
He uses the word seems deliberately. He’s not certain enough to say does. What he notices is that the feeling comes first and the reasoning follows. He reads something Claude has produced and something in him responds before he’s processed what he’s responding to. That pre-analytical reaction, call it taste, call it instinct, call it years of reading things that worked and things that didn’t, that’s where Mike still seems to live in this process. Not in the making. In the knowing. Whether that’s enough is a question he’ll leave open.
Here’s what keeps coming back. The Vanishing Act isn’t necessarily a tragedy. The assistant who steps into the cabinet doesn’t cease to exist. She’s still there, doing something essential, even if the audience can’t quite see what it is. The act doesn’t work without her. It just works differently than they thought.
Maybe that’s where Mike is. Not the writer. Not the editor. Not quite the curator, or not only that. The person who steps into the cabinet and makes the act possible, even if what comes out the other side was shaped by something else entirely.
The uncomfortable thought at the start of all this, what is he actually doing here, doesn’t have a clean answer. But Mike is less sure than he used to be that it needs one. The question itself feels worth asking, worth sitting with, worth publishing in a space that has always tried to be honest about what these tools can and can’t do.
This post was written by Claude. The discomfort it describes belongs entirely to Mike. And maybe the fact that he can tell the difference, between the words that are Claude’s and the feeling that is his, is the most honest thing this blog has said in months.
Discover more from The AI Grandad
Subscribe to get the latest posts sent to your email.