It's been like this for a long time. The very first question I answered on StackOverflow, in 2015, the accepted answer, given by someone with a reputation in the thousands, was wrong. I know it was wrong because I was working in the company providing that technology, I was an instructor teaching that technology, and I could talk to the engineers in my company directly (plus, you could just look at the open-source code yourself for the answer). The answer even claimed that the internal developers did not know the answer -- again, completely made up.
(I just looked at the question again, and surprisingly, my answer now has twice as many upvotes as the "accepted" answer. So maybe there's still hope!)
I find that there's a crowd of what I call "professional StackOverflowers" who just flood the site with half-baked answers hoping for reputation points, and those answers, which get the most points simply by getting there "first", also tend not to be the best answers.
Nevertheless, just like doing a Google search, you've got to know how to use SO effectively. For questions with multiple answers (say, a dozen), the "better" answer is often buried far below the popular, accepted answer, in almost every case where there are multiple answers. So you need to scroll down and read those answers. And often you'll see useful updates to the original answer (I know, since I provide many of those updated answers myself).
The reputation system is definitely broken, but I find that StackOverflow is still useful.
As to the "no more good questions" assertion, I don't agree with that. The area where I'm currently working -- AWS cloud technologies -- there are lots of new questions to be asked, and those technologies continue to change and evolve.
I've also not seen the toxic behavior that you refer to in your article, but I think that's because I'm operating either in the backwoods or the bleeding edge of technology where the toxic people don't hang out. Maybe it's because if you're just starting out in tech and going to a coding camp (and you're of a certain immature age), you're not going to be writing Terraform or AWS Cloudformation templates, which tend to be utilized more by the corporate crowd.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's been like this for a long time. The very first question I answered on StackOverflow, in 2015, the accepted answer, given by someone with a reputation in the thousands, was wrong. I know it was wrong because I was working in the company providing that technology, I was an instructor teaching that technology, and I could talk to the engineers in my company directly (plus, you could just look at the open-source code yourself for the answer). The answer even claimed that the internal developers did not know the answer -- again, completely made up.
(I just looked at the question again, and surprisingly, my answer now has twice as many upvotes as the "accepted" answer. So maybe there's still hope!)
I find that there's a crowd of what I call "professional StackOverflowers" who just flood the site with half-baked answers hoping for reputation points, and those answers, which get the most points simply by getting there "first", also tend not to be the best answers.
Nevertheless, just like doing a Google search, you've got to know how to use SO effectively. For questions with multiple answers (say, a dozen), the "better" answer is often buried far below the popular, accepted answer, in almost every case where there are multiple answers. So you need to scroll down and read those answers. And often you'll see useful updates to the original answer (I know, since I provide many of those updated answers myself).
The reputation system is definitely broken, but I find that StackOverflow is still useful.
As to the "no more good questions" assertion, I don't agree with that. The area where I'm currently working -- AWS cloud technologies -- there are lots of new questions to be asked, and those technologies continue to change and evolve.
I've also not seen the toxic behavior that you refer to in your article, but I think that's because I'm operating either in the backwoods or the bleeding edge of technology where the toxic people don't hang out. Maybe it's because if you're just starting out in tech and going to a coding camp (and you're of a certain immature age), you're not going to be writing Terraform or AWS Cloudformation templates, which tend to be utilized more by the corporate crowd.