The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
"Since, stackoverflow comes in top of google search results, it has a good set of QA, that doesn't mean whatever they do with new users or beginners is correct."
So what would be correct? How do you handle the large inflow of questions from users who won't bother to read FAQs, or lurk long enough to understand the etiquette?
How would you handle the users who can't be bothered to do their own research? Or search? Or think for two seconds?
How about the users who just post their homework questions? Literally, post their homework questions?
Whatever your answer is, I'm certain you'd probably do that for a little while. Maybe even a little longer than a little while, then you'll get tired of it and just start employing the mechanisms available to start cleaning up the environment.
You still didn't link to your question. With that we could help you understand why your question was a low quality question and how you could make it better.
Yes, SO as a public forum has to deal with issue of every person with an internet connection. Yes, sometimes people are just rude, or your perception of their text is that it's rude... but that's life. Do you go to SO to feel loved or get an answer to a question/problem? Focus on the latter and the former becomes moot.
I'm a happy user of StackOverflow community, I highly participate in Java Q/As mainly by answering questions. After seeing this thread and similar questions on Meta StackOverfow[^] I start thinking on what can possibly be the root of all evil (like premature optimization ).
Anyway, let me try to provide a personal opinion on all the topics covered in your post:
if a new one asks a simple question, then the top users starts down voting, ranting
Define simple question. For example, if somebody in Java asks "how can I create a hello world app" then I would post a comment saying "that's covered in a tutorial" and vote to close. This question lows the quality of the site.
Ok, another (not that) simple question: "this piece of code doesn't work code that doesn't even compile I appreciate your help." ok now this is unanswerable at all, first because the code doesn't compile, and if it does compile but there's no stacktrace, then I usually have to read through a wall of code to tell OP: "you didn't initialize foo variable, thus you getting a NullPointerException...". There goes another simple question that lows the quality of the site.
And a last example of a simple but too broad question: "how can I create RESTful web services in Java?". Again, this is an unanswerable question that can is already covered in plenty tutorials. No need to reinvent the wheel in stackoverflow.
If someone don't have knowledge on particular topic or another then the regular users start insulting them.
I'm ashamed of this, and I see stuff like that for one of the following reasons (AFAIK):
- OP is really lazy to understand the answer. You spot a question like "how can I foo the bar" then an answer posts "Use quo, it will foo the bar as you expect: Here's a sample code fulfilling the answer" and I upvote it for showing a good example, but then OP raises a comment like "ok now I need to baz the bar from foo, how can I do that?" and I reply in a comment "OP please read about how foo and baz are very close you just have to change one line it's not that hard" and OP starts complaining about me insulting and giving him the bad eye. Then, another user reads all that and provides a new answer with the line to change and he gets the accepted answer. Now we have a zombie user and a rep w**r3 vampire in the site. Ugh.
- OP is really lazy to search for it before posting a question. For example: *how can I find a String in HTML using regex?* And the common answer for this (and I agree because I also tried to do this in the past, silly me): Don't use Regex to parse HTML[^]. And you provide of this to the OP to realize that at least 4429 people around the world have suffered the same and we know this should not be done, but OP starts complaining at us that we are all wrong and that his task is so simple that he/she should use regex and there won't be a problem with that... And after some minutes (or days) OP posts that we were right...
They call themselves as experts.
Sorry, but I don't see this in the site. For really high rep users (more than 100k) I cannot see such comments or related stuff. Not even from Jon Skeet or BalusC (check about them here [^]). I have even seen users with less than 1000 rep that are experts on what they answer, but they don't say it out loud.
They are playing with site good reputation.
Not only us, but also those new users that don't read the FAQ. Specifically, any user should first read How to ask[^] section to learn how to provide an answerable, specific, not too broad, not "first result on my SEO" question for the site.
Yes, I've noticed the attitude over there as well. Since CP wants to compete with SO why not build a Knowledge Tree of posts and answers that they could quickly search and browse (and link to articles)? I have yet to see a proper Knowledge Tree structure implemented anywhere yet. And I've haven't had the time to write about it. But it's a proper and significant next generation step in the evolution of knowledge structures (another concept that needs writing about). If anyone is significantly interested I will do a CP article on this.
I like stackoverflow.com, though I have seen some limited behavior like you described. Many users are way too quick to down vote both questions and answers. I've used the site for several years and have only down voted once or twice. I reserve that for extreme circumstances such as abuse or repeating the same problems many times while ignoring question asking advice from other users.
There are a few recurring issues that people have with asking questions on there that could be helped with better research and communication skills by the askers of questions.
Sometimes there are disagreements about exactly what does qualify as a suitable topic for SO (or it's sister sites) as well as the tags used for questions. Once I asked a question on there about the using sed. Some people may have considered that question to have not been on topic because it wasn't enough of a programming question, but it was answered. If I had been asking a general user question, such as "How do I run a program on Windows 98?" then I'd probably have been down voted because it wasn't a programming question (and because it mentioned "Windows 98").
Asking a question on SO should almost never be the first thing anyone does when a question comes to mind. When you post a question there it takes up other people's valuable time to read, consider, research, and answer (ignoring the time that it takes for someone to down vote), so if someone asks a question on SO that could easily have been answered by Googling then people are likely to down vote that question because they take it as disrespectful of the value of their time. If someone does look for resources and is still confused, or even confused by the resources, then cite those resources in your question. If no resources can be found, mention what you've searched on (the keywords). It is quite common that people are calling a concept the wrong thing or at least something other than what it is commonly known as, which can make searching and asking questions not work out well.
SO is in English, so make sure that you're English is readable. It would be nice if native language wasn't an issue, but it is. If you're question makes no sense grammatically then it will be misunderstood, ignored, or down voted. People on SO will try to help fix up questions like this, and the asker needs to check back to read the changes, suggested changes, and pleads for clarity that other users have posted. Personally I often find it easier to read broken English if I know what the writer's native language is, and I suspect that is probably the case for others. At the very least it may allow you to get help communicating your question by someone who speaks your language. When writing this response I almost included an expression that is very understandable, but when translated literally might be confusing to others. That is another thing to be aware of.
Beginner programmers often have misconceptions and confusion about how certain things work that are difficult for more seasoned programmers to relate to. Most of us have been there, but it's hard to remember to try to scrutinize what someone is saying for clues about misconceptions, especially when the asker is often speaking with confidence about their unconscious assumptions being true. This is another communication issue. This often results in a question starting out as "How do I do _X_ with _Y_?" but end up being more about what Y actually is and how that's different than what the asker thought Y was.
Learning how to include relevant information without overloading with too many details about your particular instance of a problem is a skill that must be learned. It can take time, but reading other questions can help. Many times I've seen someone ask a question that included completely irrelevant information about what product they hoped to eventually have when they were really wanting to know some small detail about a programming language, algorithm, or library. Other times I've seen people leave out so much information about what they are trying to do that it's either not comprehensible to others or that it isn't clear to others that the specifics of this problem would actually fit solving the problem a different way than the asker was trying. For instance, asking how to send a message from one computer to another one over the Internet does not usually need to include what kind of information that message carried, but it may be relevant what protocols are being used, what operating systems, and how they are connected.
Another thing to be clear about is why the asker is asking the question. This may sound silly because the answer is obviously "Because he/she wants to know the answer.", but this is actually about if the asker is trying to solve a problem a certain way (and may be pursuing a more difficult path than have to pursue), doing homework (people on SO will almost never give you the answers to your homework, but they will often guide you), or just for your own understanding.
I've been on Stack Overflow both making and answering questions, and I have found it a great community overall, however, to get a good answer, you should ask a good question, this is more evident on newbies, who often ask either, to give them the code, something that has been answered multiple times before, or you realize that they don't even understand some basic concepts; most of the time I try to help them (even when they should not ask that, do a quick search or it's not the purpose of SO), but when you're on the 100th question of the same style you may start to loose your temper, in the end we're all persons, so please don't be quick to judge the whole community just because someone freaked out.
Most of the time it's because the asker didn't bother to google it while the result can be easily got within the first page. Sometimes they need to improve search skill. When they enter the question they don't even have a look at SO's suggestions while I'm sure there are tons of duplicates already.
Having read some of the Jon Skeet facts[^], based on the old Chuck Norris facts, it seems that it's time for us to do our own version here. So, I'll start you off with some OriginalGriff ones.
NASA is now transmitting recordings of OriginalGriff into space. He has prevented 8 alien invasions so far.
OriginalGriff was not born. He has always been.
OriginalGriff caused the Big Bang - it happened the last time his code failed to compile the first time.
OriginalGriff's tears are the cure for every illness ever.
Chuck Norris quotes OriginalGriff facts.
OriginalGriff IS every Stig.
Dr Who is the autobiography of OriginalGriff.
OriginalGriff knows where infinity ends.
OriginalGriff lives in Wales - the only part where the sheep aren't nervous.
OriginalGriff once wrote a simulator with a rounding error. That's why Pi is no longer 3.0.
OriginalGriff knows why it is 42
That'll do for now - we wouldn't want to embarrass him
OriginalGriff had a dodgy keyboard -which is why Queue is spelled that way.
OriginalGriff's name comes from an anagram of 'Oral Frig If Gin' which harkens back to a best-forgotten night with Nagy
OriginalGriff writes code that optimizes itself.
OriginalGriff’s first program was kill -9.
OriginalGriff can write infinite recursion functions … and have them return.
OriginalGriff’s mouse can type 140 wpm
and the best for last
When OriginalGriff is web surfing, websites get the message “Warning: This user is malicious,dangerous and OriginalGriff. Proceed?”.
I recently was approached by an intermediary firm on behalf of another company looking for Android developers. They asked me to do a code challenge and post the source code to GitHub, which I did. About 1-2 weeks later, they asked me to do another code challenge for the prospective client/employer at their request. I've never been asked to do more than one code challenge for a prospective contract/job.
How many of you have been asked to do multiple code challenges for a prospective job? This seems a bit strange to me. The code challenges are not major projects. However they are the kind that would take a full day to complete so they aren't completely trivial either. I'm trying to find out how common this is and whether or not I should assume that the prospective client/employer isn't really serious and is just "kicking the (my) tires" by asking for multiple code challenges.
I may be a bit jaded, but this sounds like a company trying to get some free stuff at your expense. Either that, or they have one or two other applicants who posted some promising work, and want to sort among you for the best. I'd go along with it one more time, but if you're asked for a third round, I'd demand a seance with the principals before complying.
they asked me to do another code challenge for the prospective client/employer at their request
Even if they are not trying to screw you, it's a stupid policy. Unless it's lot of money in question, I'd rather spend that day staring into blank space, then 'proving' my 'worth' to company like that. I mean, do you really need two days to determine if someone can code, seriously? If you need that much time, maybe you're not that good developers after all.
So I took a cruise through Oatman and the mountains behind it on the way home from work tonight, scouting for a likely place to go shooting this weekend. I am careful to look for places that are on public lands - no private property - with a good backstop, few rocks, and no vegetation, since the fire hazard is so high this year.
While hiking about a likely spot, I ran across a young woman who was obviously despondent, at the end of her rope, standing on the edge of a cliff and trying to work up the courage to jump. Naturally I was terribly concerned about such a tragic waste, so I approached her and asked,
"Miss, since it's clear that you intend to kill yourself, would you mind having sex with me first?"
She shoved me away and screamed, "You perverted bastard! Get away from me!"
I'm a patient fellow, and not wanting to cause her any further pain, I walked away, telling her on parting, "That's okay. I'll just go wait at the bottom."
You're absolutely right, Karen; it really shouldn't be in the Lounge. It's borderline, but the funny factor outweighed naughty bit. Besides, I don't know of any modern kid sister who would find it shocking or naughty. Standards have slipped from the days when I was a kid brother.