The web app I’ve been building on my own is finally getting close to Closed Alpha. I’m pretty happy about it. This time, I’ve been seriously trying to develop it in something close to a dark factory style. I say, “I want a feature like this.” AI writes the code. It writes the tests. It runs them. If something is wrong, it fixes it. I check what came out and give it the next instruction. ...
Today I read a Zenn article titled “I Built ‘yomiyasu,’ a Skill for Making AI-Slop Japanese Readable at the Structural Level.” It introduces an Agent Skill for rewriting the kind of Japanese we call AI slop into prose that feels more natural and readable to humans. And while I was reading it, I had a thought. A skill for fixing AI-slop documents feels like a terrible waste. This is not to say that yomiyasu is bad. If anything, it takes the question of what makes AI-generated prose hard to read quite seriously and breaks the problem down carefully. ...
For a while, Claude Code kept using the phrase “implementation train” in one of my personal projects. Implementation train. What the hell is that? At first, I thought it might be a real term. I had never seen it in Japanese, but maybe “Implementation Train” or something like it had become popular in English-speaking developer circles. Apparently not. When I traced it back through the old documentation, it looked like Claude Code had once compared something to a train. That sentence survived somewhere in the docs. ...
Lately, I can’t read the PRs Claude writes for me. Well, I can still understand the title. “Add feature X,” “Fix bug Y.” So far, so good. It’s the body that’s the problem. Nope. You’ve lost me. What on earth are you talking about? Maybe this is my own fault. I can’t rule out the possibility that watching too many short videos and scrolling X has damaged my ability to read long passages. ...