I've been a member for 10 years now. I racked up a few thousand points after I joined, before the novelty of gamification wore off for me. After a decade of ste

I've been a member for 10 years now. I racked up a few thousand points after I joined, before the novelty of gamification wore off for me. After a decade of steady usage, here's my take on Stack Overflow. Stack Overflow is an excellent resource when you access it from a search engine. If you're looking for a particular bit of programming knowledge and you type your query into your search engine of choice, chances are excellent that Stack Overflow results will be plentiful on the first page and that more than one will be relevant and helpful. Stack Overflow is good enough when you have a very concrete problem that nobody before has asked about before. For example, if you don't know how to do X in the framework Y, you can expect one of the following: 1) someone who did it before will tell you how, 2) someone who had the same problem and found that it actually has no solution will tell you that, or 3) nobody will answer. Stack Overflow is absolutely terrible when you're trying to learn something new just because you want to learn it or you're asking for advice of any kind. If you're trying to become a better programmer, Stack Overflow is categorically not the tool for the job. The less practical your question , the more it's likely to receive votes to be closed. My favorite example is a question that outlined a thing you can normally do in .NET and Java because they are executing bytecode and can do certain checks before deciding whether to allow the code to execute or not. The question then proceeded to ask whether there are any pre-existing solutions to do so when working with native code or whether you would have to do it yourself. It received a downvote and a vote to close within 2 minutes of being posted. The voter posted a comment recommending Software Engineering Stack Exchange as a better site. The same question posted on Software Engineering Stack Exchange got a bunch of comments, only one of which actually addressed a question to a certain degree, the rest being ideas on how to change the requirements, snarky sniping of other comments, one idea that was already outlined in the question, and one snarky recommendation to "brush up on your understanding of [concept]" where the [concept] is not the primary concern in question. I wish I could say that last anecdote is an exception, but it's simply the most egregious example of what's prevalent on Stack Overflow and programming-related Stack Exchange sites. Interestingly enough, I haven't seen it on any non-programming Stack Exchange site, so it's definitely something in our culture as an industry.