9
$\begingroup$

It's standard practice here to close questions that are too elementary to be considered "research-level". But I think people have been too quick to label some questions as "too elementary", when in fact they describe very real research-level questions. For example:

In both cases, there is an undergraduate-level "textbook" answer. (For the first question: Sorting requires $\Omega(n\log n)$ comparisons. For the second question: Hilbert's 10th is undecidable.) But if we look past those easy answers, these are legitimate research-level questions in theoretical computer science.

  • Okay, but then how does one prove lower bounds for problems that can't be solved by comparison trees? Or lower bounds bigger than $\Omega(n\log n)$ for problems solvable in polynomial time? Or exponential lower bounds for NP-hard problems?

  • Okay, but then how does one actually find integer roots of polynomials in practice? Are there effective algorithms for broad and interesting classes of polynomials? Are there algorithms with provable approximation guarantees (for interesting classes of polynomials)?

In both cases, the deeper question is likely not what the original poster intended. (But StackExchange answers are for the entire community, not just for the original poster. And why should we shy away from blowing the original poster's mind?) And even if it were, the posts would require significant editing to bring the deeper question to the fore. (But editing good questions is generally preferred to closing them.)

Should we really close such questions? Or am I just being a smartass?

$\endgroup$
  • 2
    $\begingroup$ To answer the last question with a question: would it be the first time? $\endgroup$ – Dave Clarke Jul 18 '13 at 15:28
  • 2
    $\begingroup$ No, nor will it be the last, I'm sure. $\endgroup$ – Jeffε Jul 18 '13 at 23:26
  • 2
    $\begingroup$ For what it's worth, I've opened a hopefully more clear version of the first question you posted: cstheory.stackexchange.com/questions/18426/… $\endgroup$ – jmite Jul 22 '13 at 17:26
  • 1
    $\begingroup$ have long suggested that moderators close questions only in rare cases, but the stackexchange system seems to encourage exactly the opposite, and its also highly moderator-specific. & there is tons of stuff in the meta archives here about the high close activity but apparently nearly zilch interest (and strong pushback) in changing the status quo. long ago tried to raise this issue but got shot down with heavy artillery fire. imho downvotes are more appropriate. but, some "change is in the air" with the new stackexchange changes around closing, its a systemwide issue. $\endgroup$ – vzn Jul 30 '13 at 3:12
  • $\begingroup$ fyi stackexchange close rework project faq & blog "war of the closes" $\endgroup$ – vzn Sep 11 '13 at 5:40
6
$\begingroup$

I read the first question, and it does appear to me that there's an excellent CW (or not) answer waiting to be written for it. The question is certainly broad, but I wouldn't speculate on the motives or expertise level of the questioner. It's likely that they don't have much background, but so what ? I face this kind of question in my graduate algorithms class all the time, and as JeffE points out, it's really a tricky question with very different answers.

In fact, the very idea that you need to fix a model to even talk about lower bounds is not at all obvious to students who haven't been steeped in theory for a while. It's possible to go through an undergraduate degree in CS at a reasonable place, learn that "sorting takes n log n time", and never really confront what this means until you hit grad school.

In short, there are questions where the questioner has little background and the answer is quite trivial. But then there are questions where the questioner has little background and the answer is highly nontrivial. I agree with JeffE that this is a good chance to "blow the questioner's mind" with some truly deep ideas that theoreticians have developed over the years, as well as create a general reference answer that others will be able to Google.

One issue that might have been raised with this is "well, let's let it go on cs.SE and it can be answered there". While that's something that we could do, I'm more inclined to define our scope broadly rather than narrowly (as the SE overlords have said in the past regarding the SE system in general). In other words, the fact that this question could be answered in some form on cs.SE shouldn't disqualify it from being answered here, and in fact for this particular question I think we are the more appropriate forum for expert answers.

$\endgroup$
  • $\begingroup$ Just to make sure I understand correctly, you are suggesting that from now on we don't consider "the level of background of the author" as a strong reason to close questions. So questions which are non-trivial do not need to be closed just because their author might lack background. I think that is reasonable. $\endgroup$ – Kaveh Jul 19 '13 at 5:29
  • 3
    $\begingroup$ the very idea that you need to fix a model to even talk about lower bounds is not at all obvious — ...in no small part because that point is glossed over (or omitted entirely) in most undergraduate algorithms courses/textbooks. $\endgroup$ – Jeffε Jul 19 '13 at 14:31
2
$\begingroup$

Jeff, I generally don't vote to close unless there are several close votes. But I think it should not be problematics to comment and say this looks off-topic when I think so. I usually try to even phrase such comments carefully and conditionally so the OP can reply and clarify that I misunderstood and that would be fine with me.

I think I have expressed the following before (probably as a reply to Peter in some meta discussion). I agree that there are some very knowledgeable users on cstheory who can write very deep and interesting answers even to very simple questions. I don't have an issue with this by itself and I even enjoy reading such answers. But I think you would agree with me that we have to draw a line somewhere for separating on-topic from off-topic (it doesn't need to be very rigid and black and white but it should be clear when some questions is really off-topic).

It seems to me that following what you are suggesting we should not close any question, even very basic ones, because someone might be able to write a very deep answer (independent of what its author was looking for). I am not sure if even very simple standard undergraduate textbook exercises can be closed then as I am not sure that no one can write a deep answer to such questions.

To put it in another way, my issue is this: where do we draw the line? You or some other user might like a question and might want to write or read a deep answer to it, but I can't read minds or future. I need something more concrete that I can base decisions on. I can't tell a user whose question is closed that another similar question is left open because someone wanted to write a deep answer to it although it has similar level. I don't mind if we relax where we draw the line, but I need it to be reasonably clear to be able act based on it and also categorize as off-topic those questions which others consider to be really off-topic here.

ps: if you or someone else edits an off-topic question and makes it on-topic that can be fine. However, IIRC, we had a discussion about this long time ago and the result was that if someone has a related interesting question they should post it as a new question. I personally don't edit such question except in very special cases for two reasons: 1. I don't think it is good to edit someone else's question so much that it is not what its author is looking for. 2. I feel that this might open the door for more similar off-topic questions.

$\endgroup$
  • 3
    $\begingroup$ It seems to me that following what you are suggesting we should not close any question, — No, that's far too extreme; most closed questions deserve to be closed. In particular, I see no way to salvage these recently closed questions, even barring cross-posting issues. But can you really not see my two examples as leading to a potential PhD thesis? $\endgroup$ – Jeffε Jul 18 '13 at 23:32
  • 3
    $\begingroup$ In particular, having written a PhD thesis myself on that precise topic, I feel strongly that the first example should be reopened and answered at face value. No editing is required to make it an interesting research-level question. $\endgroup$ – Jeffε Jul 18 '13 at 23:49
  • $\begingroup$ @JɛffE, the issue with the second question is resolved. the first one is more delicate and I will discuss it in another comment. I agree they can lead to PhD theses. But the possibility of leading to a PhD doesn't look like a workable criteria to me. Maybe it is possible for you and more senior people who have advised and judged PhD theses that there is a clear distinction between these two and other questions but as someone who is still working on his own PhD it is not that clear to me. I cannot reply to someone who objects to a closure with I don't think your question can lead to a PhD thesis $\endgroup$ – Kaveh Jul 19 '13 at 4:23
  • $\begingroup$ One possibility is to consider these as gray area questions. If you or others think they should be reopened for some reason (like those you explained) then you can vote to reopen and ask others to do the same thing. There is no problem with reopening a closed question. We might disagree about suitability of some questions and that is also fine. $\endgroup$ – Kaveh Jul 19 '13 at 5:24
  • $\begingroup$ Regarding the first example, I personally think there are two issues with it: 1. there is no evidence that the author is familiar with basics, 2. it seems to be too broad. The first one has been an accepted reason to close questions I think (we can change it if there is enough support for that and say that from now on "the author of question not being familiar with basics is not a good reason for closing questions"). For the second issue, I think it can be addressed if the question is edited and becomes a reference request for study on the topic. I think that can be a fine question. $\endgroup$ – Kaveh Jul 19 '13 at 5:28
  • 2
    $\begingroup$ "Too broad" is a reasonable criticism of that question, but "the author doesn't know the basics" is not. Answers are not for the person who posts the question, but for the community at large. (And yes, of course, it's fine if we disagree.) $\endgroup$ – Jeffε Jul 19 '13 at 14:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .