This happened in the conversation channel where I discuss blog drafts with Kimiko-chan, my nickname for ChatGPT.

“Let’s build a project management tool!” I announced.

I wanted a tool for managing the programs involved in a piece of work as a group. So I declared my intention right there. It was rather like bringing a toolbox to the desk where I keep my story notebook.

The gray-haired author character in a green shirt holds a toolbox between a writing desk and a laptop desk.
AI illustration: a metaphor for separate writing and development spaces, not an actual portrait, room, or software screen.

Then I caught myself.

“This is the daily blog draft channel. Is it really the place to build a project management tool?”

I decided to create a separate channel for development and ask for help there. Article discussions here; tool-building discussions over there. Even with the same Kimiko-chan as my conversation partner, I would give the two activities separate spaces.

But separating them did not end the matter. I had another idea.

“Let’s turn the development process in that new channel into a blog story about building tools with generative AI.”

I had moved the development discussion out, then immediately planned its return as a story. I had not even stumbled yet, and I was already looking for something to write about!

What I decided at that point was to separate development from writing, and to make the development process a subject for future articles. This was not the unveiling of a finished tool.

Build it first. Then write about what I actually considered and changed. That is the order I want to follow.

For now, the toolbox goes to the other desk. The story notebook stays open.

Based on my decision, recorded in the blog draft conversation, to give development a separate channel. This is not a report of implementation, completion, or measured results.

WRITTEN BYYoshio Taki

IBM i / AS/400 System Engineer