I think SO and MF (Meteor Forums) share many of the same pros and cons, and it seems to me that we may be in the first stages of the ātroubleā that SO faces when a topic sticks around long enough. Namely, that the members of this community who are most active in helping out could become frustrated with seeing the same questions over and over, etc.
Say I have a problem with my app. Itās throwing an error, but when I google the error, I get a bunch of different answers from different sources. I even see some on SO, but the replies are from 2013, so Iām not even sure they would be relevant. Instead of sifting through the answers, I simply post a new question and hope that someone answers it. If the question gets flagged, then maybe I start sifting through the answers, or maybe I take to another community (MF?) and post there.
Thereās no boilerplate for asking questions, so I pop in here (MF) and post my question, with the generic error Iām seeing. Someone helpful responds, asking to see my code, and I reply back with a block of unformatted code. Someone else replies, asking me to use this stuff
, so I do. Now Iām a few hours into this bug fix, but at least real people are talking to me, and Iām not poring over google results trying to figure out which one actually fits my case.
Finally, someone helpful on MF gives me the mongodb syntax fix I need, and things are back to being great! But in all actuality, this exact question was asked just a few weeks ago on MFā¦
A real life example:
This was a good back and forth between a pretty new user and one of the super helpful people on MF: Help with routing
But, when I am creating an almost identical post, the post I linked to above doesnāt pop up:
Iām no expert on Discourseās algorithm for topic/post suggestions, but Iām wondering if a boilerplate structure for help questions wouldnāt help users find the answers they need before asking another question?
Also, maybe taking some of the top SO questions/answers and compiling them into a FAQ or stickies here, with answers that are updated to reflect the most recent changes, best practices, etc.
I think SO is a very valuable source of information, and itās interesting to read through questions with a number of useful, varied answers ā this has been a great way for me, personally, to learn about the ways in which others think about code.
However, I think for many of the reasons mentioned above, SO can seem hostile, especially to users who are new to a platform. I think MF may be a good place to strike a balance between:
A) asking users to do a little bit of work when trying to solve a problem
and
B) making the best use of the knowledge and time of the community members
Just my two cents