How do you make your users read the README before asking you solutions already proposed in the README?

@alex ☎️: “IT department, have you read the README and turned it off and back on again?”

@alex There are in my experience so far two possiblities a) by rephrasing the readme so that it makes sense to a newbie and they actually see the solution b) there is no second possiblity - if people don't read basic stuff, you cannot make them

@tomterl yeah, it's a cultural thing I guess, to go straight to click/type/build instead of making the effort of actually reading the instructions first. Or a human flaw. Or even an evolutionary feature that favoured esploration over reflection? whatever it is, I think you're right, not that much to do about it, beside ranting on the Internet of course 😂

@alex @tomterl In my experience, you can't win this battle.

There was one time I shamed someone and yelled (all caps in work chat) to ask if he knew how to read. He responded that he legitimately did not read it even though he had the page open. It became awkward and I tried to apologize and he said I didn't need to because it was his fault. He'll surely remember that... but was that a win? Or am I the guy that's too risky to talk to?

@greypilgrim @tomterl simple answer: if you lost your calm, you lost that battle

@alex The Minecraft server does this funny thing where you have to actually flip a Bool in the EULA.txt before the server will actually -run-. It's the first thing the server .jar checks for on runtime. It'll generate folder structure but will not initialize the rest of the process until eula=true.

I've also seen it where the password to 'activate' the software is hidden inside the, and you can't start it otherwise. And CTRL-F wasn't helpful.

So uh... you have options. 😏 :ac_joy:

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.