It's weird that both sites' communities have made it difficult for old users to take part, but in completely different ways.
[1] https://www.quora.com/Which-is-the-best-WordPress-plugin-to-...
I mean, I get that SO wants to be a programming resource (as in "archive") where people with a problem should find a solution - not by asking but through googling. And so they want question/answer pairs that have a sort of general value, not an individual answer to just one person.
But then again: why? What's the big deal? Someone has a very specific question, and maybe nobody in the universe will ever have the same question again, but I'm willing to help that person out -- why shouldn't I be allowed to do it? Are they really worried about too much noise on the site? Please, come on.
In the situation I sketched above, I will still walk away having learned something new, but the person who posed the original question is left with a very negative user experience AND is none the wiser regarding their specific problem. At the same time, I was never allowed to help that person which I wanted to do not for the potential credit points but rather for altruistic reasons. Way to go.
Is this really so hard to believe? I have been a member of the community for ten years now (https://goo.gl/JZkqSP) and have seen the number of low-quality questions rise to the point where I honestly don’t enjoy answering any more. People don’t care to ask well, they just want to get over their personal issue as quickly as possible and be done with it.
It may well be true that the number of low-quality questions is increasing (I believe it, some really are just garbage), but the number of low-quality reviewers has unfortunately also increased.
When nearly every question I end up on has been closed it seems they don't really care, if they did closed questions would disappear.
The product itself has also become 1000x worse to use and I think it's one of the biggest examples of a Silicon Valley company that remains successful despite the constantly bad product management.
Anything that is spam worthy, like marketing or self help, is pretty much junk.
But other topics on there are fascinating. I read a few weeks ago an account of someone's grandpa who was an SS officer in Nazi Germany.
If you have an interest in a topic that isn't typically spammed by 'gurus', check it out on Quora.
Especially in the JS space[1], there are lots of historic answers upvoted on SO that are now wrong and you have to scroll around (or find a slightly rephrasing of the same question that occurred more recently) to find a good answer. Unfortunately the longer a question is around both the more answers it has and the more likely the answers are to be wrong. On forums / mailing lists the question would just be reasked. On SO it is supposedly a wiki so new versions of the same question gets closed.
[1] Because it has evolved a lot, Rust has similar issues, as I'm sure lots of languages do
I really do try my hardest to keep old questions and answers relevant. Stack Overflow allows editing Q&A for a reason, and any time I stumble on an older post, I at least think about updating it.
One thing that I've occasionally found frustrating is that someone sees a question was asked 2 years ago and thus assumes that it must be invalid / out-of-date. They simply don't look at the edit dates.
Remember that Rust has a pretty strong backwards compatibility guarantee. Any answer using only the standard library in the last 3 years should still be valid (crates are a different concern). If you find a question you think has become stale, add a bounty to it to raise attention — that's the SO recommended path of action.
We also have a Rust chatroom on SO where a bunch of regulars hang out and people are welcome to pop in and ask if a Q&A is still valid.
A lot of the editing I do is to improve the grammar, reduce fluff, use Rust-standard indentation, improve the formatting, include complete error messages, update links, etc. None of that should affect users of older versions other than to make it easier to get to the core content of the Q/A.
When a new Rust feature comes out, usually the original part of the answer gets a header denoting the compatibility. https://stackoverflow.com/a/28953618/155423 is such an example.
Note that SO does keep a revision log of edits (e.g. https://stackoverflow.com/posts/28953618/revisions) to a post. You can browse that if you think there might be something hidden that's worth exploring. This doesn't necessarily help with search engines, of course.
I have nearly given up looking for JS answers in SO because they are such garbage these days. I am learning Rust right now and still find answers on there useful.
We actually have a specific tag for those cases (`rust-obsolete`), so if the question / answer cannot be rehabilitated for Rust 1.0, that's a useful thing (I also try to add an in-question disclaimer to make it easier to spot)
And how many of those slight rephrasings never got a chance to get a more relevant, correct, modern answer because they were marked as a duplicate?
- they get marked as duplicates, so that all future people coming in via Google get funnelled to one place
- that place gets new modern, more relevant answers
- they get voted up because they're useful
- people add comments about answer compatibility
- they either overtake the other answers and the other answers stay around as history, or if they don't there is a single place where relevant answers can be found.
1 question with 10 answers is a lot more discoverable than 10 questions with 10 answers.
One leads to 9 answers to skim-read and ignore and 1 answer to use.
The other leads to you finding 6 questions and 6 answers you don't like and 0 answers to use and missing 4 you didn't know existed.
In SO, re-askings are not allowed, but as the question becomes less and less similar at some point it will be allowed. The problem is that "canonical" question for that problem is really just the first one that came along, and there are no good tools for keeping it up to date. It doesn't matter how much karma you have, there are no tools for getting rid of highly upvoted or marked as correct answers that are now wrong / dangerous. So the trick is to find similar but different answers that approach the problem in a more modern way, but haven't been closed as being dupes.
In forums, re-askings are expected and if you ask a JS question 10 years later you will get answers relevant to the time. Posts are not expected to be evergreen, so you can look at when it was asked and have context as to the environment it was asked in, as opposed to SO where the date is sort of meaningless because it's sort of a wiki.
If you know the modern answer, you can downvote the bad old answer, add a comment saying "answer is wrong/dangerous", flag for moderator attention, or edit it and correct the answer, or add your own answer as well even though the question is 'answered'.
Re-asking a question is worse - then there's that big famous first answer with 75 upvotes prominent on Google. And your question/answer with 1 upvote and a "correct" modern answer.
Nobody will find that.
But it's a good point - if you don't know the modern answer and want to, and you can't "re-ask" for new input, then what?
Sometimes you have to work out the underlying Q is and answer that even if the OP doesn't want to hear it.
And often times you have people trying to "work out the underlying Q" leaving your question still open but with useless answers.
About that, there seems to be a recent trend that answer quality is so low that the only actual useful information is on the comments.
I swear these people must sit F5-spamming their review queue, just itching to flag every question possible. They really make it an unpleasant place nowadays.
Hey, you have to earn those sweet internet points somehow... Gamification has its downsides like this.
It would help showing that in your question. Often questions lack the necessary information to discern whether the asker has actually covered the basics
> [...] how you know there are other ways you could do it but you're constrained toward this direction for various reasons
Answerers are also programmers that like to apply best practices whenever possible. If you want to do something unusual which might smell a little without explanation your colleagues, code reviewers or similar would probably also ask "is this really necessary?". So you either have to write defensively from the start or deal with the patronizing-but-wellmeaning-comment-downvote-edit-reopen ordeal.
It's unfortunate, but there is an information asymmetry. The answerers can only see what you write, while you have all the background information specific to your case.
And you don't feel the same thing when you comment on HN?
I honestly think every point you made about SO can also be said of HN, reddit and almost any other place where people congregate online.
This is how the system is designed, IMO. It's the encouraged behaviour.
Hmm, we really remember things differently. I remember:
- Answers locked behind paywalls (ExpertsExchange)
- Searching pages of forum threads.
- Answers spread across multiple posts
- "Nvm, I solved it" https://xkcd.com/979/
In my experience, finding answers to programming questions is in a much, much better state of affairs now than it was in 2007.
I routinely cringe at reading some of the comments on SO, the general smugness on there. However there's no comparison to the past options. It's better in every way. Forums of old were overflowing with plenty of smug behavior as well, SO didn't spawn that.
This does not help when offering basic advice on employment out side the USA you will see I highly rated posts go on about "right to work" - this has Zero if not negative value and could actively cause harm.
StackOverflow has saved the shit out of so many developers. What would a junior engineer do without an SO thread?
How dare they feel smart huff puff
Because it really sucks to spend half an hour on an answer and then op goes "actually I'm doing this" and the spec shifts completely rendering your effort wasted.
A few times of that, and "clarify your question so it's very clear what you're asking" is a lot cheaper.
To quote myself in a comment on a now-closed question just yesterday:
> Your desired output would be invalid json anyway, what are you actually trying to do?
You really can't answer something reliably when the asker is posting things that don't make sense.
This is exactly how I feel about asking a question! Except "Actually I'm doing this" is "why don't you do that" or "why are you doing this" etc.
> Because it really sucks to spend half an hour on an answer
My feeling is that they aren't answering the question though, not the core one, there finding a thing that you're wrong about and talking about that instead.
It's like taking the above paragraph and refuting it by saying "*they're". Yes there is an (intentional) spelling mistake in there, but is that really the point of that it's trying to say?
"How do I parse x from some text my code is (pile of code)"
"you could do y approach (code with example test) but it might break in z condition will you have z condition?"
"I'm trying to get a result from this"
"Well if you'd said so there's a built in way to do that directly exasperated"
Is that "not answering the core question"?
That, I feel, leads to "why are you doing this?" style comments.
Are you really talking about spelling nitpicks? Because anyone can edit questions to correct that kind of "clarification" and I do see people quietly doing that to help questioners with mangled markdown formatting and similar
Totally.
> Are you really talking about spelling nitpicks?
Sometimes. I'm trying to be vague because I don't want to pick on specific examples, but what I really mean is nitpicks that are irrelevant to the core question.
For me the core pain felt like:
- Askers working out how much context to bring to a question
- Answerers not presuming there is more context to the question
- The ensuing fight spread over answers, re-edits and comments, leaving a gross complicated passive aggressive mess at the end of it
So you don't want to explain your entire life story, and when you encounter problems you usually aren't working on something that easily compresses into 20 lines of code. So there is expected and undestandable challenge in compressing your example. Not bringing too much context is also important, because you're trying to ask one specific question, not the hundreds of potential questions in your codebase.
But often times I feel answerers will take your example, presume it's literally that, even with `foo` and `bar` as classnames or whatever, and take it completely as face value and then point out why it's obviously stupid, even when those stupid things are ancillary to the main point, and there only because it's compressed example code.
Extra context to my opinions here: I haven't seriously contributed to SO in at least 5 years. I probably ask 1-2 questions a year now, and do so with great trepidation. Grain of salt and all that,
Asking a question on SO is a last resort to me, and I get a horrid sinking feeling in my gut when I feel forced to do so. The people[1] who are still active on it seem to be people who thrive on pedantry and whose goal is to find any potential flaw in your question and feel smart for pointing it out.
You begin to realise no one is actually reading your question in good faith, so you start getting defensive: filling your questions with disclaimers about how your example code is just an example[2], how you know there are other ways you could do it but you're constrained toward this direction for various reasons[3], and so on and so forth, until you feel like you spend more time defensively shoring up your question from attacks than actually constructing the question in the first place[4]
I still read SO, but as someone who was around before it existed I don't really feel like the quality of answers is any higher than the random forum posts of yore, it's just that they're all under the same URL now, and the same user interface.
Which I suppose is something.
[1] Not all people™, but definitely the general feeling tends this direction
[2] classic situation: you simplify your code to Foo and Bar levels to show the problem cleanly, so people chastise you for having a complex data structure / worrying about performance / whatever for such simple code
[3] e.g., "How do I achieve X" gets turned into people saying "Why would you want to achieve X, that's stupid"
[4] This is not the same as researching the issue and trying as many things as you can think of, which is definitely helpful in any context of question asking