Stack Overflow is about collecting "high quality" questions and answers so you can quickly google for answers to common questions. For instance I can google for "error FS0030: Value restriction" and most of the top answers are from Stack Overflow and more or less answer the question: "How do I fix this error?"
Following the goal of collecting "high quality" questions and answers, Stack Overflow does not care about answering your question. Unless your question is useful to more than just you. Stack Overflow is also limited to specific code tactics and errors, not general conceptual questions.
SO's Software Engineering site can be used to ask more conceptual questions, but I find it somewhat broken for that purpose. They are trying to apply the SO curation formula they use for tactic/error questions, and it just doesn't work. To start, the site gets a lot of the wrong kind of questions based on misperception of what it's for. (Software Engineering means anything to do with code right?) So moderators are constantly having to close a lot of questions which don't fit on the site. Also, conceptual questions are far more nuanced, and may require a bit more explanation. But these larger/deeper questions hinder the ability to moderate and answer them with single answers. Many require a conversation to answer. And many times the moderators are not familiar with (or perhaps don't like) the concepts being asked about, which has a negative effect on the question. I've seen answerable questions closed as too broad or opinion-based due to ignorance, or moderators post salty comments/answers about concepts they don't like (which then gets upvoted by other mods). It is not surprising because the constraints of the site setup a strong tension between moderators and question-askers.
So anyway, I actually like this site in lieu of the Software Engineering site, because #discuss questions and answers here are more free form and can take a conversational approach. But Stack Overflow is still the best thing out there to look up errors, tactics, and specific tech usages. And I don't see that changing any time soon.
Following the goal of collecting "high quality" questions and answers, Stack Overflow does not care about answering your question. Unless your question is useful to more than just you.
This is the main thing people don't understand about SO. If your question doesn't serve the community it will probably not be well received.
This focus makes it very good at some things (e.g. hosting fantastic solutions to all sorts of problems) and very bad at others (e.g. helping beginners). Dev.to makes a different set of design/community moderation decisions which results in a different set of tradeoffs. Both sites have their place.
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.
Stack Overflow is about collecting "high quality" questions and answers so you can quickly google for answers to common questions. For instance I can google for "error FS0030: Value restriction" and most of the top answers are from Stack Overflow and more or less answer the question: "How do I fix this error?"
Following the goal of collecting "high quality" questions and answers, Stack Overflow does not care about answering your question. Unless your question is useful to more than just you. Stack Overflow is also limited to specific code tactics and errors, not general conceptual questions.
SO's Software Engineering site can be used to ask more conceptual questions, but I find it somewhat broken for that purpose. They are trying to apply the SO curation formula they use for tactic/error questions, and it just doesn't work. To start, the site gets a lot of the wrong kind of questions based on misperception of what it's for. (Software Engineering means anything to do with code right?) So moderators are constantly having to close a lot of questions which don't fit on the site. Also, conceptual questions are far more nuanced, and may require a bit more explanation. But these larger/deeper questions hinder the ability to moderate and answer them with single answers. Many require a conversation to answer. And many times the moderators are not familiar with (or perhaps don't like) the concepts being asked about, which has a negative effect on the question. I've seen answerable questions closed as too broad or opinion-based due to ignorance, or moderators post salty comments/answers about concepts they don't like (which then gets upvoted by other mods). It is not surprising because the constraints of the site setup a strong tension between moderators and question-askers.
So anyway, I actually like this site in lieu of the Software Engineering site, because #discuss questions and answers here are more free form and can take a conversational approach. But Stack Overflow is still the best thing out there to look up errors, tactics, and specific tech usages. And I don't see that changing any time soon.
This is the main thing people don't understand about SO. If your question doesn't serve the community it will probably not be well received.
This focus makes it very good at some things (e.g. hosting fantastic solutions to all sorts of problems) and very bad at others (e.g. helping beginners). Dev.to makes a different set of design/community moderation decisions which results in a different set of tradeoffs. Both sites have their place.