All you are doing here is injecting your own over-weighted bias into the algorithms and creating yet another tyranny of moderation for everyone that culminates with every single online community monotonically decreasing off peak from the point of its inception. Moderators should be more -- if not entirely -- concerned with tweaking algorithms rather than tweaking members and activity directly.
You may believe the current rules and moderator brute squads work to keep the site clean, but from where i'm standing they work to make the site useless.
Nobody seemed able to know what a high quality question was, nor could come to an agreement on what topics specifically would be allowed.
I left the community and became a mod a year later because stackexchange asked me to - given that I had a high reputation on the site and the site itself was in danger of dying out. The site still exists today IMO, in spite of the users who are quick to criticize other peoples questions instead of answer them - and really because the topic itself is something a lot of people are interested in without a lot of other communities to go to for support.
Stackexchange's system encourages people to be bitchy and put down other people's questions. They are in the position they are because of SEO - and because google and yahoo's alternative solutions were short sighted. If the monetization model was really all that strong they would lose their market position very quickly.
It's good that there are rules, but what really matters is the community. People are on there are trying to get help following their passion or making their living. The stakes are often very high for the asker, making a rude response particularly painful.
I was messing around with Elixir (which is newish in the scheme of thing) and it's very different than asking about Rails/Ruby.
[0]: https://en.wikipedia.org/wiki/Wikipedia:WTF%3F_OMG!_TMD_TLA....! [1]: https://en.wikipedia.org/wiki/Wikipedia:Article_half-life [2]: https://en.wikipedia.org/wiki/Eternal_September
When the site clearly looks like as a place for noobs to get questions answered for free then maybe don't complain that you get just that.
If you are starting out with something new, someone has already had the same problem you are. Your question has already been asked and answered.
Instead of searching for specific jargon they don't know about they'll come up with their own terms to try to explain their problem.
This is another acquired skill, nowadays to be a good programmer you need to learn how to search for documentation and how to phrase it and to learn that you need to become a programmer and be in contact with the technical jargon.
I don't know another way to overcome this except for experience, what is exactly what newbies don't have so I try not to bash them but educate in how they can find the stuff they want.
IMO we are talking about every newbie that find SO every day and those who don't like dealing with them.
[0]: ok, that last one was on networking stackexchange or something.
Pretty clear that it's for professional programmers and not beginners. I agree that it is a bit frustrating to google something and have the SO question marked as a duplicate of another unanswered question. There are many places to learn the basics of programming and SO is not that place.
SO itself begs to differ:
> Stack Overflow is for professional and enthusiast programmers, people who write code because they love it.
So very clearly not only professionals.
Also as lambda points out somewhere in this discussion you might be a seasoned pro in one language and a noob in another.
However, I have been discouraged from using the site in recent years due to too many disagreements over closing and downvoting questions when actually just getting a little bit more clarification from the person asking the question would have helped a lot more.
I've answered over 1,000 questions, ranging from very simple beginner level to some things that took a good deal of research or debugging to answer. I've seen my fair share of poor questions. If a question is completely off topic, then sure, I click the "close" button immediately.
However, if it's on topic, and about some identifiable issue, but not specific enough, too poorly worded, or doesn't include a code sample, or the like, then I post a comment requesting clarification, and listing how they can improve their question. In some cases, they actually work with me, improve the question, and then I or someone else can answer it. In some cases, they just ignore my comments or continue with requests to just give them the code or the like, in which at that point I find it worth a downvote or close vote.
But a lot of the times, I've seen perfectly good questions that were just a little confusingly worded, however I was able to tease out what they were getting at, I've done some research to find the answer, and come back, only to find the questions closed. Now I have an answer for the question, but can't actually post it. If I vote to reopen, sometimes even after editing it to clarify or getting the OP to edit it, it will generally languish with one or two reopen votes. Sometimes I'll then post on meta to complain about this behavior; people being way to quick to close. This will frequently lead to enough people clicking through to reopen it, but also a torrent of complaints about how the question really is bad and how we shouldn't let this kind of stuff on the site because it's destroying the community.
The thing is, bad questions don't destroy the community. If they're bad questions, they'll generally fall off the front page and get forgotten about. They don't really cause much in the way of problems; they're just a few extra bits. But this hostile behavior does destroy the community. It pushes beginners away, who may ask better questions later once they get a bit more of a handle on what they're doing. And it pushed people like me away; people who are there to help, and willing to do so even for beginners.
I think that Stack Overflow is a very different thing than MathOverflow. Professional programmers sometimes run into thing that they need to do that they are complete beginners at; you may have years of experience writing Java, but then you wind up needing to integrate with and write a plugin for something written in Ruby, and you really have very little experience with it and so don't know where to look. Due to the huge numbers of different languages, APIs, platforms, and so on, rapid pace of change, and shortage of qualified people with the exact relevant experience, almost everyone is a beginner at something they are doing at some point in their career.
Furthermore, some people just don't know how to ask good questions online. It's a skill that takes some time to learn. If you're asking a question to someone in person, they may already have more context about what you're doing, or will be able to more easily ask you questions to clarify and sit down with you to work through it, while asking good questions online can involve a certain amount of preparation in advance to narrow the issue down to a self contained, reproducible test case, to phrase the question appropriately, and so on.
So while I agree that complete junk should be closed and delete, and people who just post "plz gimmeh teh codez" should be discouraged, I am really frustrated by the way people extend that to things that are just beginner questions, poorly worded questions from people who aren't good at asking questions online or aren't good at English, or the like.
Sure, there are typos, and the question could be worded better. But is it the kind of question that deserves the “fuck off” it got?
(0) Don't downvote newbies to oblivion. That's just being a bully. (IMO, downvotes should be reserved for bad answers.)
(1) When contributing an answer, provide an option to flag the answer as “taken straight from the manual”. I'll call such answers “RTFM answers” for short.
(2) When a user receives their first RTFM answer, just tell them in a gentle way that they're expected to do their research, and perhaps provide useful links, depending on the tags associated to their question.
(3) Only if a user consistently asks questions with RTFM answers, punish their behavior in some way: reputation loss, decreased question visibility, etc.
I've asked my fair share of dumb questions and even posted dumb answers, and the community has treated me relatively kindly. (I have ~7k reputation as of now.) I wish others could be treated the same way.
Of those questions about a day old with score <= 0, only ~30% are less than 0. Of those <= -1, only ~30% are < -1 and only ~10% are < -2.
Your RTFM tag doesn't seem to add very much over a moderate count of downvotes. I believe the rest of what you've said applies when downvotes happen.
Great, so you've learnt something for next time.
> Beginners need guidance. They’re dumb and they flail around and they get stuck on “easy” problems. That’s why resources like Learn Python the Hard Way and Stack Overflow exist in the first place.
Sorry, but no. "Stack Overflow is for professional and enthusiast programmers, people who write code because they love it." Stack Overflow's biggest problem is that frequent contributors are getting fed up with the torrent of newbie questions from people who haven't programmed for a month.
Imagine joining Math Overflow because you're an enthusiast mathematician... only 19 of every 20 questions are about how to multiply two digit numbers. Imagine joining a DIY group after years of practice only to find that you spend most of your time building cubes out of playdough and sticks. Have you tried reading the new queue on Stack Overflow? What does this[1] even mean? (I'm actually kind'a shocked about how good it's looking right now; only about half of the questions are utterly irredeemable.)
People from the outside don't see this. There are filters in place and people who care to make them work. So all you see is the hostility and none of the reason. But please believe me when I say that it's not just us being cronies. We really do care about the site, and we just don't want to lose it.
[1]: http://stackoverflow.com/questions/37779153/how-to-enable-di...