Skip to main content
SubZeroDev

Professional uncertainty since 2026.

Well… Why not?


I Asked It to Publish a Fucking Story

· 4 min read

How a simple journal entry became a full-scale repository management incident.

I had a story to tell.

Actually, I had several.

I spend a fair amount of time talking about my life, my projects, my experiences, and the general absurdity of being alive in a world apparently managed by an understaffed committee of drunken monkeys.

Sometimes those conversations contain something worth writing about.

So I created a Journal skill.

The concept was straightforward.

I talk.

The AI examines the conversation.

It finds stories worth developing.

It presents them to me.

I choose which ones I want.

Then I decide whether I want the original material lightly edited or transformed into a full narrative.

Once the stories are ready, I can tell it to publish them.

Marvelous.

I also created a completely separate skill called Note.

That one has a different purpose.

When I discuss a project, describe an idea, or establish something worth remembering, Note captures the information in my private Notes repository.

It's knowledge capture.

Not storytelling.

Not blogging.

Not publishing.

Two fucking workflows.

I thought this was reasonably clear.

Apparently, I underestimated the creative interpretation capabilities of artificial intelligence.

Because one evening I invoked Journal and watched the process start exactly as expected.

It found the stories.

Asked me which ones I wanted.

Asked about the editing style.

So far, so good.

Then everything went completely fucking sideways.

Somewhere along the way, the AI decided the correct destination involved private files in my Notes repository.

Now, don't misunderstand me.

I have absolutely nothing against drafts.

If I tell the system to create unpublished drafts, I expect drafts in the blog repository, typically through draft pull requests.

That way, the content exists where it belongs, but it hasn't been published to the website.

Perfectly ordinary software development practice.

What I don't expect is for the assistant to take my journal articles, put them somewhere else, and then tell me they're safely stored as though that's the accomplishment I requested.

It gets better.

When I started questioning the behavior, the assistant began explaining my own workflow back to me.

Apparently, I had asked for private storage.

Apparently, I hadn't authorized publication.

Apparently, there were configuration concerns.

Apparently, there might even be missing skills.

Every explanation led to another explanation, and every explanation moved us farther away from the original task.

At one point, I was informed that the skills might not be available.

Excuse me?

The same skills I'd been using repeatedly?

The same skills that had already produced published articles?

The same fucking skills that had worked just fine the day before?

And then there was the computer.

Suddenly ChatGPT appeared to be doing something on the machine.

What?

I had no goddamn idea.

Why?

Excellent question.

Was it modifying files? Navigating GitHub? Running some elaborate recovery operation?

Who the fuck knows?

I certainly wasn't getting a meaningful explanation.

I had asked for a journal workflow.

Now I was apparently supervising an autonomous expedition into my computer.

And this is where the entire experience became almost artistically absurd.

I wasn't trying to solve a difficult engineering problem.

I wasn't attempting some groundbreaking experiment in artificial intelligence.

I just wanted to take a personal conversation, turn part of it into a story, and publish the fucking thing.

Instead, I found myself arguing about repositories, workflow definitions, authorization states, and what the assistant thought my instructions meant.

By the end of it, I wasn't writing anymore.

I wasn't publishing anymore.

I wasn't even particularly interested in the stories anymore.

I was debugging the system I'd built specifically so I wouldn't have to manually manage the process.

And that's a hell of a way to destroy the motivation to do something creative.

I started the evening wanting to tell stories.

I ended it trying to understand why my storyteller had become a confused repository administrator.

Next time, perhaps I'll ask the AI to reorganize my infrastructure. With any luck, it'll accidentally write a fucking novel.