I've noticed that on StackOverflow most of the questions are of the "how do I do x on y".
This site gets a fair number of those, too, but there are a lot of design questions that really need a lot of wrangling.
Quote:
|
I find that it is hard to get answers on this site because there is little or no incentive.
|
First, let's be honest. If you take the time to ask a well thought out question, you usually wind up answering your own question. Database theory and practice is similar to math in that the way to answer a question is usually to frame the question correctly.
Most of the time if a question pops into your head, it's pretty stupid to just type it into a box and expect a person to answer it. But that's what a lot of people do.
10% of the time, the question is almost complete gibberish, or it looks like the person stopped halfway through.
70% of the time, I find the answer in the first page of Google results. Or the answer is clearly in the documentation. And we usually do point the person in the right direction. lmgtfy.com is a great resource.
Of the remaining 20% of questions, maybe half of them are fairly vanilla design questions or queries. The other half tend to be really obscure stuff. There are a lot of years of experience here, but we just don't know everything.
So what will a point system do? For gibberish, nothing. For obscure stuff we really don't know, again, nothing. Or worse: people might make up a fake answer just for points.
I predict you'd get a lot of "karma-whoring" on the easy google-it / documentation questions and passing over the interesting questions because they're a lot of work for the same points.