Our first list question

We got our first list question. We need a policy how to deal with this and similar questions.

Also, how to tag it? Not everybody likes .

• big-list works on cstheory. think the se fmt actually encourages lists. suggest that policy not be created until an actual (bad) trend is observed. a single question is not a trend. think (along with DC) reliance on case-by-case voting generally is better. – vzn Apr 7 '13 at 23:55
• @vzn Theoretical Computer Science is an exception for many things because of its focused, engaged user group. Every single list question we have had on Computer Science has produced more crap answers than good ones. – Raphael Apr 8 '13 at 8:02

Real questions have answers, not items. Reading lists don't work well in the questions and answers format of Stack Exchange. With one item per answer, you end up with voting that combines how old an answer is (utterly useless), how popular it is (mostly useless), and how good and relevant it is (if you're lucky). Your proposal removes the impact of age, but it requires heavy duty maintenance: we'd have to watch every list question, check how the voting goes; and in the meantime we have this jumble of answers (many of which will be in the provisional stage for a very long time).

For book lists covering a topic, we have a place: the tag wiki. There is a Stack Exchange-wide move to put book lists in tag wikis, and better support for large tag wikis is in the plans.

Other book questions may be acceptable, but only if they call for useful answers. That is:

• The question should express a specific need. Not “all the books/the best books on topic X”, but “I want to study X, what combination of books/articles would give me good coverage?” — where X is narrower than a whole sub-discipline.
• Answers should strive for completeness: never give a single item unless you claim that this single item is sufficient in and of itself. An answer that adds just one book as a complement should be an edit to an existing answer or a comment.

I recommend reading the Literature Stack Exchange book recommendation policy (which kinda works, but still lets a lot of mediocre questions with mediocre answers in) and the Programmers Stack Exchange book recommendation policy (which… well, it's Prog.SE).

Community wiki is not an excuse for bad questions. If the question is good, it doesn't need CW. If the question is bad, CW won't redeem it, it needs to be closed.

We don't need to tag these questions specially. If the question is good, it doesn't need to be ghettoized. If the question is bad, a tag won't redeem it.

Regarding this specific question, I initially voted to close, but I've halfway reconsidered. I think it may be barely ok. The good thing is that it calls for a limited syllabus (we're not going to recommend 100 books). On the other hand there are already 6 answers, of which only 1½ really address the question; the other answers just take this opportunity to mention their favorite books. Furthermore, the lack of a tag (no, is not a suitable tag) is a bad sign.

• 1) From this discussion I took away that lists are not per se bad. 2) Does tag wiki ensure proper peer review? 3) I think some of your remarks are overly general and do not relate to the question at hand per se. – Raphael Mar 18 '12 at 2:13
• And, most importantly: What do you suggest? How should we deal with the question? – Raphael Mar 18 '12 at 2:14
• @Raphael I thought you were proposing a general policy, so I replied to the general policy. I find the question borderline. I wouldn't shed a tear if it was closed, though I'm prepared to let it live. It does need moderation; it is attracting bad answers like flies (the proposed books may be good, but they do not answer the question). – Gilles 'SO- stop being evil' Mar 18 '12 at 2:17
• I am happy to moderate it but we still a clear, somewhat sanctioned policy so I don't have to take rude behaviour like Dai's. – Raphael Mar 18 '12 at 23:17

In the light of this discussion, this is what I propose to do: