r/javahelp • • Apr 29 '16

What is Stackoverflow's problem?

I'm a beginner to Java - every time I post a question on Stackoverflow I am greeted by a torrent of downvotes or I get my post put on hold/edited/marked as duplicate for some reason even when I read everything relevant first, even though this doesn't help me. I thought this was a place where we can ask questions, I seem to get quick responses and get help some of the time but why is this community so assholish? I don't understand the purpose of the website if they are like this?

32 Upvotes

30 comments sorted by

27

u/Sacredify Apr 29 '16

Stackoverflow is notoriously anal about things like duplicate posts and whatnot - there is a lot of criticism about how their moderators operate the place (search /r/programming or google for a few lovely examples of why people don't like how its run).

That being said, in most cases there generally already has been a question that asked the same thing - the problem is, half of them are years old; you just need to know what to search for.

21

u/[deleted] Apr 29 '16 edited Apr 29 '16

Yes, the site works in a strange way :

  • Simple questions have already been answered, so newcomers can't get "points" unless they answer more advanced questions. And you need these points to have access to voting or commenting. So Stack Overflow is much more of a closed club than it seems to be.

  • Most people mark questions as "not specific" or "duplicate" only because they can, or because they want to argue with other members about how derivative the question is in relation to a somewhat similar question. And these posts appear in your Google research rather than being deleted.

  • The validated question often is the first thorough answer, even if it isn't quality code. So you often have this strange situation where a very beginner validates the answer of a beginner, then professionals argue for years why the answer isn't good enough or the question should have been closed in the first place.

  • Very specific questions are left hanging because people who have proficiency with a less popular language or implementation don't get much upvotes. And SO has this gamification where upvotes increase your "score". If you are a TCL programmer, you won't answer many questions, thus you'll have a low score and feel your input is less rewarded by the community.

  • Lots of ego battles.

4

u/SkloTheNoob Apr 29 '16

or only the description is similar and your problem completely different and or requires a different version of the API.

12

u/desrtfx Out of Coffee error - System halted Apr 29 '16

Stackoverflow is a great community, but not really for beginners.

The problem with SO is that they are very strict about the quality of their posts as well as about duplicate questions (which they have a somewhat strange definition of because anything that is even tangentially related to any old question is often flagged as duplicate).

SO wants high standard, well formulated, well thought through, well researched, and well formatted questions.

They actually have guidelines (that I can't currently find) on how to prepare and write questions there and they stick to those standards.

Now, for a beginner, these high standards are a problem as a beginner often doesn't even know what exactly to ask and how to ask properly. That's why reddit is more beginner friendly - we will try to help as long as the question is somewhat understandable and shows that the poster has spent some effort researching.

Generally, the key to successful questions is the way they are asked.

  • A question that gives the impression that the asker "has tried nothing and is all out of ideas" will generally fail, here and worse on SO

  • A vague question will fail

  • A question that shows zero effort will fail

So, in order to get a successful question with satisfying answers one needs:

  • To prepare the question well - basically in such a way that it includes as many details as possible

  • Include all that one has tried so far, both, in code and in sought resources

  • Display that they have spent effort researching and solving the problem

Often, when spending lots of effort in preparing such a question, the solution comes at hand - this is also known as Rubber Duck Debugging - basically explaining the question to an inanimate object that has as much knowledge about the subject as a rubber duck. By doing so, one has to think deeply and in a different way and thus often the problem can be solved.

Again, the above (Rubber Duck Debugging) is a problem for a beginner as they often lack the ability to explain their problem well - there is no blame here, this is a natural process. Beginners find it hard to express themselves well because they simply lack the vocabulary and the experience to do so.

If you look at our posts here, you will see lots of low quality, extremely vague, no effort posts that get trashed as well - but for different reasons than on SO - here, we try to encourage people to learn and to work, but some people misuse the sub as "do my homework" or as "too lazy to google". That's the reason for this post.

Even here, you will see the proverbial "What have you tried?" quite often. This has two reasons: without knowing what OP has attempted already it is difficult to determine their level and also it forces OPs to actually do something (or display that they have done something other than sitting and waiting to be served on a silver platter and spoon fed).

5

u/[deleted] Apr 29 '16

TIL rubber duck debugging, thanks.

4

u/desrtfx Out of Coffee error - System halted Apr 29 '16

I'm dead serious about Rubber duck debugging.

It sounds stupid but it really works. We use it a lot at work (even though the "inanimate objects" that normally rubber ducks resemble are colleagues who are not involved in certain projects).

The process of explaining at a low level often gives new perspectives and since it requires a lot of thinking to be able to formulate the problem in such a way that an uninvolved (and in the case of a rubber duck unintelligent) target understands the problem helps solving.

6

u/[deleted] Apr 29 '16

I don't own a rubber duck, so my poor code-illiterate girlfriend becomes the subject of my verbal debugging. She's not crazy about it. I think I'm getting a rubber duck for my next birthday...

4

u/desrtfx Out of Coffee error - System halted Apr 29 '16

Rubber Ducks are mandatory equipment for programming ;)

2

u/Targom Apr 29 '16

Ours is a rubber chicken, nobody is really sure where it came from. Well, a few people are sure where it came from; however, their stories don't match so I assume nobody knows where it actually came from.

2

u/desrtfx Out of Coffee error - System halted Apr 29 '16

Wait, you in software have RITA??

That, that, that's all wrong... RITA belongs to the networking team. Wonder who messed up the deliveries...

2

u/Targom Apr 29 '16

Maybe it was stolen from a networking team and that is why nobody "knows where it came from"

1

u/desrtfx Out of Coffee error - System halted Apr 29 '16

Or did you have one of the Purple Boxes and your company was one of those customers?

4

u/[deleted] Apr 29 '16

I take you seriously, it also happened to me. It doesn't surprise me : one of the best way for learning something is to have to explain it to someone else. I didn't know this was named like that ^

3

u/themoose5 Apr 29 '16

^ this 10/10

The amount of times I've been stuck on a problem and just being curious my girlfriend has asked me a question about what I'm working on or what I'm stuck on and as soon as I go to explain it to her I come up with a new way to attack the issue. Sometimes that idea works, sometimes it leads to another idea that ends up working. Either way solves the problem almost every time.

Sometimes it just helps to verbalize problems to clear your head.

1

u/BubbaRWnB Aug 22 '16

I just figured I would add that this works for a number of reasons. First is that verbalizing something uses a different part of your brain than thinking about it. Second, as u/desrtfx touched on, if you are explaining something to someone who has little to no experience with what you are talking about you have to conceptualize what you are working on and then translate that into terms that your subject can understand. An inanimate object can be used as a subject, but any person that can ask questions that force you to look at the problem from a different perspective would always be preferable.

3

u/programstuff Apr 29 '16

Great response. Just adding my own anecdotal information to yours:

One of the best learning methods is successfully asking a StackOverflow question that doesn't get downvoted and warrants a response. I have started writing countless questions there where by the time I've finished writing it I've already answered my question by deriving information from other relevant posts. If I haven't then I feel I have a legitimately new question.

When writing the post link to other relevant information and start explaining why that post doesn't help you with your current problem, and by the time you're done you'll either have a solid question or have found your answer.

Same goes with explaining the code you have, what you want it to be doing, and why you think it might not be doing what you want it to do. Again, by the time you finish that process you either have a solid question or have found your answer.

Rubber duck debugging is definitely a real thing though I find typing out a detailed question to be more helpful than talking to my ducks.

20

u/denialerror Apr 29 '16

I think a lot of people new to programming don't realise how important Stack Overflow is to professionals. I probably visit SO every day in my job and although I'm new in my career, I have colleagues that have 30 years experience and still visit the site regularly when they come across something new.

And this is where you start to appreciate the anal nature of how SO is run. If I want to find something in a hurry while trying to fix something for a customer, I don't want to have to wade through multiple duplicate questions or badly worded answers. I want to type what I want into Google, click on the first link and read the first response. Without SO's moderators being meticulous about their rules, this would not be possible.

14

u/basalamader Apr 29 '16

Someone told me " that the best way to learn something as a beginner is to ask as a last resort".

The reason to this is because it forces you to search for the right question. Honestly, sometimes finding the right answer is not about getting the code but more about asking the right question. I think that's why stack overflow seems pretty anal about that. They reason that, "this is something you can search for, why should we do the work for you". It sucks..

4

u/mariox19 Apr 29 '16

Early on, when I started to learn programming, I asked a really smart programmer friend of mine for some help with a bug in my program. He showed me what I was doing wrong, how to do it right, and then a simple and more elegant way of doing the same thing. (He introduced me to the idea of using a lookup table instead of nested if-else statements.) That was the first time.

The second time I asked him for help, he gave me this piece of advice: "Be stoic." As much as I appreciated his first bit of help, I appreciate his second even more.

Look, I've asked for help on forums many times; but usually that's only after not solving the problem on my own after a lot of research on my part. Aaron Hillegass (the founder of Big Nerd Ranch), in one of his iOS books, recommended that a person first try to write a toy application to explore and solve a problem. He said something like, "It'll take you 15 minutes, and as often as not you'll solve the problem. If you don't, you'll at least understand it much better so as to be able to ask better questions."

The worst mistake a person can make in programming—or anything else, for that matter—is to just throw up one's hands and cry, "I don't get this."

2

u/basalamader Apr 29 '16

I actually don't disagree, asking is better than giving up. I think the problem comes in when someone is a beginner and has a problem that most programmers encountered as beginners. There is a high chance someone asked that problem before you and there is a high chance a more experience programmer answered it. The problem of being a beginner in my opinion is you don't know what to search. Most people will put the code on the board and say something of the sort "I keep getting this error...Error:...."

I think part of being a programmer is not finding the right solution but sometimes finding the right question to ask. If the person for instance looked at his code base and had an idea of where the error was, they would ask something different like hmm I wonder why this specific thing isn't working and Google that.

2

u/mariox19 Apr 29 '16 edited Apr 30 '16

Knowing what to ask is difficult for the beginner programmer. It's difficult enough for the experienced programmer using some new technology, but at least at that point you probably realize that there is something you don't know.

6

u/nutrecht Lead Software Engineer / EU / 20+ YXP Apr 29 '16

SO is not for beginners question. It's actually designed and moderated against this. So no it's not somewhere where you can just ask any programming question. If you get downvoted don't take it personally.

It's intended to become a more or less static repository of knowledge. If they let in too many "low quality" questions it would dilute the quality too much (similar to how you end up with a ton of bad hits on google when you search for something).

Yes a lot of the people there are assholes but that doesn't change that you're using SO for something it's not intended for. So by all means, if you have questions ask them here or on /r/learnprogramming. Reddit is more suitable for personal help on questions that aren't that interesting for others.

4

u/[deleted] Apr 29 '16

Next time you need to ask a question remember doing these steps before you even start typing:

  1. Thoroughly search for an answer before asking your question(google/learnprogramming/javahelp/etc...). Note down what you have found. You will undoubtedly get better responses by telling them what you have found in your research. Also, nearly every beginner you can think of has been answered.

  2. Know what topics you can ask and remember to not ask these type of questions. Don't just post your code and then ask people what is wrong with it.

  3. Be specific in what your problem is. Explain it as thoroughly as you can because this will certainly stop the bad responses.

Source

Read through some questions that have been solved and look at the way their asked.

5

u/strmrdr Apr 29 '16

Your beginner questions are better suited to a place such as this sub. Stack is more of a "professional" site where real devs are asking tough questions, with the newbie ones either already answered in some facet via other posts or dozens of other websites. If you're asking why you're getting a Null Pointer on Stack, for example, you're going to have a bad time (we here will likely be more willing to help you).

If you gave us more context as to what you were asking, or a link to your question, maybe I can tell you specifically why you were getting shat on.

2

u/[deleted] Apr 29 '16

Stack is more of a "professional" site where real devs are asking tough questions

Sure, but beginner questions are also greeted with proper answers if their problem is unique to their use-case in such a way that a generic answer won't help them much. This is, however, entirely contingent on the delivery of the question. They are strict with things like formatting, question ambiguity, etc

2

u/Your-Ma Apr 29 '16

Throughout my 4 years in College i had 17 accounts banned from Stackoverflow.

As much as i hated having to setup a new email everytime i can see that there is no other way of providing a platform that has the best answers. I honestly think it gets the quickest answers aswell.

Part of my college experience was actually learning how to ask questions on Stackoverflow. A couple of the basics would be never delete a question with answers and if it looks like a duplicate put a note in explaining why its not a duplicate. Dont just jump in and ask without even bothering to search first. Also if you get a warning saying that some previous questions were not liked do not ignore it and correct your mistake.

2

u/avianbc Apr 29 '16

Once you hang out on SO for a bit trying to answer questions, youll notice that a large majority of them are horrible quality.

  • Bad formatting, impossible to read questions.

  • Questions that are devoid of actual questions or are way too vague

  • Obvious duplicates (null reference exception?)

  • Duestions where the author hasnt even tried to solve the problem and instead wants you to do all the work.

  • Super specific questions that will not be useful at all to future googlers (Why does this massive batch of spaghetti code not work?)

It remains hard to provide good quality answers when wading through this stuff even when the question does not fall into the above categories. Its garbage in, garbage out.

1

u/thescientist13 Apr 29 '16

Do you have an example?

-2

u/[deleted] Apr 29 '16

It's quite simple. Most of them are massive arseholes. But they are arseholes to everyone. So don't take it personally.

If you don't know what to search for how can you search for a duplicate question? Seems like they don't understand or appreciate the use case where you have a problem but can't verbalise it. Instead of walking you through the problem most will be dicks to you.

I say this whilst having had great help from the site. It's a love hate relationship with me.

As others have said perhaps that's the wrong place to ask for help at your level?

1

u/ggleblanc Apr 29 '16 edited Apr 29 '16

Seems like they don't understand or appreciate the use case where you have a problem but can't verbalise it. Instead of walking you through the problem most will be dicks to you.

Stack Overflow does not exist to be a free tutor for beginners.

Beginners can ask their questions here, at least until everyone is sick of explaining a null pointer exception or why the main method can't be found (when they spelled it Main or forgot the static keyword).