The right thing for @StackOverflow to do would be to stop labeling things "answers". They're more like "guesses", and calling something an "accepted answer" is misleading because all it actually means is that somebody who by definition isn't an expert thinks it's correct.
-
-
Replying to @cmuratori @StackOverflow
Why such a negative take on it? Even if they are guesses... guesses of the "hive mind" are far better than your own guess. Poorly documented tech in 1990? Maybe USENET will help you out, else you are stuck forever. In 2020? S/O often has the solution on a silver plate.
2 replies 0 retweets 0 likes -
Replying to @BramStolk @StackOverflow
Casey Muratori Retweeted foone
It's not a negative take on Stack Overflow. It's a negative take on their labeling. People need to be aware that they will have to do more research, otherwise you get this:https://twitter.com/Foone/status/1229641258370355200 …
Casey Muratori added,
3 replies 1 retweet 5 likes -
So some helpful warnings and nomenclature changes would help people perhaps understand that if they use something they found on Stack Overflow without understanding it, it may well contain a critical error.
1 reply 1 retweet 3 likes -
This feels a bit like “caution: hot” to me. We can’t possibly label every potentially erroneous source of information. Instead, we should work to demonize the culture of using code you found on the internet in your product without understanding what it does or testing it.
1 reply 0 retweets 0 likes -
But "caution hot" is actually pretty good, if the thing is hot? I honestly don't think most of the people who use Stack Overflow realize that a lot of the answers are wrong. I've come upon several wrong answers myself. It should be labeled more as a "bad examples" or something.
3 replies 2 retweets 5 likes
Like there is no question that Stack Overflow does the _opposite_ of this, right - they _market_ it like the answers are good. But they're pretty mediocre. I mean, I don't know, I like having things like mandatory ingredient labels?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.