[awesome_dude]

Got it - ask questions, but not ones that you already know where the answer is.

edit: well, except when you search the documentation and get (literally) 70+ results because you don't know the exact phrasing used in the self hosted wiki...

Or, when it's a question that is domain specific (meaning that the SME is supposed to know it, which you only know if you are... an SME...)

etc

[mmh0000]

Provide context when asking.

: “hey bob, I looked here and here and here and didn’t find the correct information. Can you show me where to look or tell me the answer so I can document it”

Because most people don’t bother doing the tiniest amount of their own research before asking dumb questions it becomes a huge headache to answer the same thing a million times.

However, if you can show that you did put in the effort to look up the answer first people will be much more willing to help.

[awesome_dude]

So far I have two examples (in this thread) of people making (potentially toxic) judgements about the fact that someone asked a question

Can you show why you assumed that what you are asking for wasn't provided?

Can you also explain why your response is to make rather harsh judgements rather than work out what was going on in the first place?

[awesome_dude]

You can tell that this is a toxic environment because I am getting voted down, by toxic individuals, for pointing out that people in this thread have made the massive misjudgement of claiming that the blame for the issue lies in one person - despite having ZERO knowledge of the actual context of the responses received (and spoken about in the gp), or questions being asked.

Which pretty much sums it up doesn't it.

[watwut]

> Got it - ask questions, but not ones that you already know where the answer is.

More of, ask do the quick google search or check the doc before asking that question. If the quick search or look into the doc does not contain the answer, ask.