alt Hacker News> There are other tools in this space. Worth naming plainly instead of pretending they don't exist.
Why do LLMs like this kind of writing? Why did you need to “plainly” name the competition as opposed to “flamboyantly” naming them?
This is a cool idea but the README is absurdly not-to-the-point.
Replies
Fair, you're right. Thanks for the point. I used ai for a chunk of the build and writing. However, the actual work behind it wasn't AI-generated. I spent a few weeks interviewing people in r/devops and some compliance subs about how they actually test backup restores, and the report schema especially came out directly out of those conversations. You are also right about the REAME. I'll tighten it up right now, and enhance it. Thank you for the feedback.
I think this is more Claude writing than LLM writing. GPT-5.6 also talks like an LLM, but not like this.
With GPT-5.6 I get reasonable results with "use natural, plain English". I tried "use ASD-STE100 Simplified Technical English" but I've found "natural plain English" to work better. Still not on the level I would write, but better.
In the mean time, I hear that Claude resists changing its writing style. A PO used Claude to write release notes and it was full of Claudeisms and tried changing the text into a TED talk. Then he prompted Claude to rewrite in ASD-STE100 Simplified Technical English, and Claude barely changed its writing. Then he switched to GPT-5.6 Terra, and GPT revised everything and made the text much better.
It seems to be a self-instruction. Leak from reasoning token into output token or using output token for reasoning. Perhaps something accidental like constraining number of reasoning tokens leads to model using output tokens for reasoning or perhaps ensuring some minimum user-visible reasoning. Seems like an accidentally introduced artifact.
“I should not pretend other implementations don’t exist. I should name them plainly.” Unable to tell itself that it puts this in output so that it can tell itself there.
Same with the “not X but Y” style. It is self-steering introspection leaking into output for one reason or the other. Recent poor language use by model is probably an attempt to minimize this by being concise. But it really needs more thinking to solve problem and so it does some of it in output.