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

View all comments

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.