347
The Fall of Stack Overflow
(observablehq.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Jul 2023
347 points (100.0% liked)
Technology
37702 readers
566 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
I don't entirely agree that more and better documentation removes bugs, problems, questions, concerns, or cuts too much into a 50% drop in site usage. Having documentation is just another tool in the toolbelt, to be used alongside community forums.
Discovery process for myself and many of my coworkers has always been; Look up obscure errors, problems, etc. to get an idea of what I'm dealing with, and then off to the documentation.
They don't remove bugs, but it is easier to solve them without having to wait for some random guy to answer on stack overflow.
I don't know now (I haven't asked a question in ages) but to get a good answer on stack overflow it used to take weeks sometimes
GitHub issues are usually more useful