2 ms·
> I've noticed there was a strong push around 2016-2018 to recommend newbie programmers NOT to go to Stackoverflow, but instead to ask the questions straight in
by shagie 6y ago
> I've noticed there was a strong push around 2016-2018 to recommend newbie programmers NOT to go to Stackoverflow, but instead to ask the questions straight in the Github issues. Turns out, the problem was low quality questions all along, and that just converted an issue that StackOverflow had solved long ago into burnout for open source developers on Github.
I would contend that Stack Overflow hasn't solved it. The "close poor questions" and "why are there so many people who don't search first?"
As users felt that their questions weren't answered as promptly enough on SO or that closing their questions was equivalent to gatekeeping. This lead many of the people frustrated with not getting support type questions answered on Stack Overflow to go to other places to ask those support type questions. As the tooling around GitHub issues as support has been poor (and the number of people asking questions far outstrips the number of people offering support), this is leading to burnout.
This is very much a "push it over there" problem. There's been a good bit of history of companies and libraries trying to make Stack Overflow their support site ( https://meta.stackoverflow.com/search?q=reach+out+is%3Aq https://meta.stackoverflow.com/search?q=reach+out+is%3Aq )
> Github needs to step up their game and give authors more powerful tools, there's so many entitled developers out there that will come and demand changes. It might make new devs feel less welcome, but the balance is tipped way too much to allow anyone to create massive spam for projects right now.
Absolutely - though that only delays the problem until the entitled developers overwhelm that tooling.