Yeah but a lot of people don’t really know what SO is for. They think you just go there and get help and call it a day. But the entire point is to produce structured questions, discourse, and answers aimed at future readers. Super specific, no-context, or duplicate problems are not useful. If you are not trying to generate useful content, don’t go to SO.
Just look at all the people getting frustrated at being told “you should probably do it a different way.” They really don’t understand that just because they’re asking the question, it’s not all about them.
The idea of SO is a little awkward too I think. With something like Wikipedia we’re presumably in an academic mindset. Carefully gathering information, sources, structuring it all. And even then people can get turned off by the ‘bureaucracy’ or nitpicking or whatever.
When people show up at SO they’re probably more in a “I can’t figure this damn thing out!” mode. We’re struggling with a problem, keeping a bunch of junk in our head, patience being tested, but we’re still expected to have a bit of academic rigor in our question and discourse.
Because the people who are answering questions there are doing it for that ideal of having a knowledge repository. No one is helping you because they think you and your specific problem are so important to demand their time. Especially with very tricky errors.
Not SO or it’s methods, I mean the human experience. It can be awkward to be new to it all and to feel the frustration/tunnel vision associated with being stuck on one problem… and then step back and have to dissect your issue, structure your question correctly, etc.
It’s just how it is, for exactly the reasons you stated. You can capture every little problem people face in programming, or you can hone in on useful patterns in goals, problems, and solutions, and educate people on how to see these things.
Yeah maybe SO should have this kind of warning when you’re writing your problem or question, or maybe it does already (it’s been a long time I posted a question myself).
In any case, it is an interesting case about a tricky social problem to solve. I used to listen to the SO podcast many years ago, and they always had multiple problems to deal with. One of them was to show the experts good questions, because beginner questions really turn off the experienced people and too much of that would drive them off the website, and at the same time beginners don’t have the habit of searching duplicates etc. so it’s common to spam the website with duplicate.
At some point they also restricted questions about opinions, because they lead to never ending threads with no objective answers. I’m sure they had a reason for that based on SO history, so the baggage if restrictions start increasing for newcomers to understand the rules. It’s tricky to balance the needs of power users and casual users because they’re often conflicting.
Just look at all the people getting frustrated at being told “you should probably do it a different way.” They really don’t understand that just because they’re asking the question, it’s not all about them.
I don’t agree. I remember having a problem (something with PDF and JS if I remember correctly) and I had some restrictions (no I could not do anything about those restrictions). Someone on SO had asked my question with somewhat the same restrictions, which boiled downed to no being able to utilize the most common solution. The first answer on SO was to use the solution that specifically could not be used.
I can see your point and I actually somewhat agree but when the answers are “do X” to the question “how do I do this when I cannot do X?”, the audience should be the minority going there because they have a niece problem, not the majority that are lead there by search engines. And all the “do X” answers should be removed, or moved somewhere they are relevant.
Yeah but a lot of people don’t really know what SO is for. They think you just go there and get help and call it a day. But the entire point is to produce structured questions, discourse, and answers aimed at future readers. Super specific, no-context, or duplicate problems are not useful. If you are not trying to generate useful content, don’t go to SO.
Just look at all the people getting frustrated at being told “you should probably do it a different way.” They really don’t understand that just because they’re asking the question, it’s not all about them.
I’m not saying you’re wrong, I’m just saying it’s not the friendliest way to enthuse beginners to this way of working.
I get it’s frustrating, but when you’re asking your first question ever, it feels like paying for everyone else. xD
The idea of SO is a little awkward too I think. With something like Wikipedia we’re presumably in an academic mindset. Carefully gathering information, sources, structuring it all. And even then people can get turned off by the ‘bureaucracy’ or nitpicking or whatever.
When people show up at SO they’re probably more in a “I can’t figure this damn thing out!” mode. We’re struggling with a problem, keeping a bunch of junk in our head, patience being tested, but we’re still expected to have a bit of academic rigor in our question and discourse.
I don’t think it’s awkward, it’s kinda necessary.
Because the people who are answering questions there are doing it for that ideal of having a knowledge repository. No one is helping you because they think you and your specific problem are so important to demand their time. Especially with very tricky errors.
Not SO or it’s methods, I mean the human experience. It can be awkward to be new to it all and to feel the frustration/tunnel vision associated with being stuck on one problem… and then step back and have to dissect your issue, structure your question correctly, etc.
It’s just how it is, for exactly the reasons you stated. You can capture every little problem people face in programming, or you can hone in on useful patterns in goals, problems, and solutions, and educate people on how to see these things.
Yeah maybe SO should have this kind of warning when you’re writing your problem or question, or maybe it does already (it’s been a long time I posted a question myself).
In any case, it is an interesting case about a tricky social problem to solve. I used to listen to the SO podcast many years ago, and they always had multiple problems to deal with. One of them was to show the experts good questions, because beginner questions really turn off the experienced people and too much of that would drive them off the website, and at the same time beginners don’t have the habit of searching duplicates etc. so it’s common to spam the website with duplicate.
At some point they also restricted questions about opinions, because they lead to never ending threads with no objective answers. I’m sure they had a reason for that based on SO history, so the baggage if restrictions start increasing for newcomers to understand the rules. It’s tricky to balance the needs of power users and casual users because they’re often conflicting.
I don’t agree. I remember having a problem (something with PDF and JS if I remember correctly) and I had some restrictions (no I could not do anything about those restrictions). Someone on SO had asked my question with somewhat the same restrictions, which boiled downed to no being able to utilize the most common solution. The first answer on SO was to use the solution that specifically could not be used.
I can see your point and I actually somewhat agree but when the answers are “do X” to the question “how do I do this when I cannot do X?”, the audience should be the minority going there because they have a niece problem, not the majority that are lead there by search engines. And all the “do X” answers should be removed, or moved somewhere they are relevant.