AI writes a B report at best, I conclude after writing this book
My Own Answer to “Letting AI Do It”
There are voices in the world raising concerns about letting AI write papers, letting AI do assignments. I teach at a university and a high school myself, but honestly, I can’t work up much heat over it.
The reason is something I learned firsthand while writing this book. What AI produces in its raw form usually still has something “left to be desired” — some shortfall, some rough edge. As it stands, it doesn’t pass.
So here is how I’ve come to interpret it. A B-grade report can be written by AI. But if an A+ report comes out, that’s probably because the student put in a reasonable amount of their own hands and brain.
This Book Was the Proof
The book itself is the evidence. With AI as part of the team, the first draft came together at tremendous speed. But—
- I filed over 500 correction requests on GitHub
- The survival rate of the originally generated text dropped below 70% by the middle of editing
- Japanese-language polishing left me thinking more than once, “it might have been easier to just write it myself”
Leaving it entirely to AI would never have gotten us here. In the end, human hands and human judgment always lifted the work up that final notch. That’s probably true whether it’s a paper, a report, or a novel.
A Side Note: The Oddly Endearing Side of AI
Given the nature of my development work, I’m quite familiar with tools like Claude Code. I use them routinely. And yet — or rather, precisely because I’m so familiar with them, I can say this — if you don’t watch carefully and just leave everything to it, you fall into unexpected traps. I’ve experienced this many times. Whether it’s code or prose, left unattended, it can charge off in some odd direction with a perfectly plausible face.
And yet. Once I notice the trap and lay out an improvement plan — “here’s the problem, here’s how it should be fixed” — the subsequent correction happens at blazing speed. The aimless wandering from moments before vanishes, and it fixes things precisely. This sense of “transforming the instant the instructions get sharper” is, I think, the oddly endearing side of AI. (laughs)
Here’s a funny story. Right before publication, I rebuilt the e-book, and the print-version PDF I’d worked so hard on vanished entirely. The culprit was a single line buried at the top of the build script: “delete the entire working folder.” What was supposed to be just building the e-book ended up wiping out the KDP submission PDF along with it. I went pale. But once I laid out the policy, “let’s switch from wiping everything to only rebuilding what’s changed,” the fix itself was done in no time. Point out that the first fix was insufficient, and the second time it nails it precisely. It screws up fast, but it also recovers fast.
In the end, the shape of things here was exactly the same. A human notices the hole and decides the direction; AI is the one who sprints forward from there at tremendous speed. As long as you don’t get that division of roles wrong, you won’t find a more reliable partner.
Closing
A book I started on a whim ended up taking me much farther than I expected. The idea, the development process, the reality of editing Japanese, the publishing work, the cover, the meaning packed into it — thank you so much for staying with this long series.
And now, the content itself. Please follow James Brennan’s 14 years after being reincarnated into 1980s London, in the main story.
Originally published in Japanese at https://clazytech.com/2026/07/1677/. Translated with LLM assistance and reviewed before publication.