Nobody Reads Your Setup Docs(hanzilla.co)
hanzilla.co
Nobody Reads Your Setup Docs
https://hanzilla.co/blog/mcp-onboarding-ten-agents-one-command/
22 comments
That's a no from me.
“ And I realized my setup instructions weren’t documentation. They were a wall between my product and the people who wanted to use it.”
Assuming this was written by a human, I think it is time to retire saying “this is not x it is y”.
The moment I see that I think the text is AI generated and I lose interest.
Assuming this was written by a human, I think it is time to retire saying “this is not x it is y”.
The moment I see that I think the text is AI generated and I lose interest.
It feels ai-written, for sure. The sentence structure and idioms are very typical of ai writing these days.
Agreed; I don't think "Not X, but Y" is a reliable tell on its own, but taken as a whole TFA set off my AI writing spidey-sense big time. The intro takes three paragraphs of fluff (ironically) to say "My product used to have long docs, but after using a product with much shorter docs it made me reconsider my approach."
i've noticed recently i actually do that fairly often. so i'm consciously trying to edit after the fact to remove it for that exact reason.
is annoying.
is annoying.
On a recent project we joked "developers can't read". Occasionally we'd ask for help and be pointed to the docs "I can't read".
I suspect there's two big parts to this:
1. Users expect batteries included and that everything "just works" the first time.
2. The language you used differs match your audience. E.g they search "gray" and find no results, however you've spelt it "grey"
I suspect there's two big parts to this:
1. Users expect batteries included and that everything "just works" the first time.
2. The language you used differs match your audience. E.g they search "gray" and find no results, however you've spelt it "grey"
I'm going to ask a lazy question, don't you need a good setup document in order to write the installer that executes setup?
So, how do your users uninstall it when they don't want it any more?
Regarding skills:
just symlink them. Since opencode and codex share .agents/skills use that for the others also. Just the hooks and mcp integrations are still proprietary. codex needs a config.toml setting, but then you can use eg safe-chains everywhere.
Regarding setup docs: Put it into an .deb and .rpm, put them on a free webserver, and no need to check for updates or setups.
Regarding setup docs: Put it into an .deb and .rpm, put them on a free webserver, and no need to check for updates or setups.
Isn’t that the first one reads, when one wants to Setup? What changed?
The first one i read is README
If a "developer" can't manage to read one paragraph in a readme, maybe the "developer tool" is not for them. As much as I usually hate gatekeeping, basic reading comprehension is a skill I'd happily gatekeep at.
Gatekeeping is much maligned (and not without reason), but I think that the results of no gatekeeping have proven far worse than the gatekeeping ever was. Sometimes, if someone can't put the effort into something, they should be shut out.
Just have an AI make a video out of it, I guess.
Replace the manpage with a tiktok clone. Every video clip is a different section of the manpage. /s
Okay I'm building this.
Claude reads them.
Why do people keep creating MCP servers.
All you need is bash
All you need is bash
quangtrn(1)
lol too true, learned this the hard way
In this day and age, I find it interesting that no one is screaming about security and privacy concerns about this which is so prevalent on any social media platform including this one.