Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
I have a question, maybe someone here knows the answer. On Stack Overflow we have clear documentation on what a good answer and question looks like. Is there anything like that for this Stack Exchange site?
@EdwinAshworth Responsibility for duplicates falls first, but not entirely, on the person asking the question. This question is not closed, so initially it doesn't appear to be a duplicate. It would require the execution of search queries to ascertain, whether or not, it is a duplicate, consequently, I would argue that it was not so apparent — or "clear" as you put it — that it was a dup. To address a similar subject, I don't understand why this question hasn't been closed due to a flag if it is in-fact a dup. Did you flag it as a dup?
@Tchrist I read your profile, and I really enjoyed it. Way to go on your co-authoring of your book. I live in Sebastopol where the O'Reilly is located. On a more relative subject, I was wondering if there was any source that gives some sort of general description as to what an appropriate question for this site looks like?
@Nasch first of all, this question was closed because it request a very specific domain of knowledge. Which is an accurate reason for closing the question. As much as I enjoyed answering it, I felt like I was answering a question on Stack Overflow. He was asking to describe a system. Describing systems is the very essence of what a programming language does.
If it seems like I overly defined the word enumerate, or like my answer is too verbose, then you probably don't share the love for the English language that I do.
