Skip to main content

Timeline for answer to When is Stack Overflow going to stop demonizing the quality-concerned users who have made the site a success? by Tschallacka

Current License: CC BY-SA 3.0

Post Revisions

14 events
when toggle format what by license comment
Sep 24, 2024 at 22:03 comment added Karl Knechtel @NathanTuggy "Does anyone really close Java questions as dupes of PHP questions? Seriously?" - tags for questions can be wrong. Many programming questions are not actually about any particular programming language, and should have been tagged language-agnostic - but people don't think of doing so, and take the implementation language they happen to be using, even if it doesn't matter for what they're actually asking.
Jun 9, 2023 at 1:39 comment added Karl Knechtel "The people who forget that this is a site to help people, to give answers to questions to people can understand" - the purpose of the site is not to, in some nebulous way, "help people"; it is specifically to maintain a repository of high-quality answers to questions. Answer quality entails that answers are accessible to (understandable by) the people that would most likely have the question. It also entails that questions are not duplicated and that answers are centralized. If the best existing version of the question has unsatisfactory answers, add your answer there.
May 2, 2018 at 11:28 comment added Lundin When closing as a dupe, you can still leave a comment explaining why. "On line 99 you do x. Don't do that. See the linked duplicate for details."
May 1, 2018 at 17:06 comment added Tschallacka If only inviting to chat was easy. Oh, and you might have forgotten the purpose of comments. Asking clarification, providing suggestions and answering on those.
May 1, 2018 at 16:44 comment added zero298 Then invite them to chat instead of having an edit/comment/answer war trying to figure out what the OP was actually asking for. Those kinds of questions, typically, aren't useful. I downvote answers that are trying to guess at what the OP wanted because they aren't answers, they are guesses. That's the whole point of the comments: get clarity on the question. Once you have the question actually nailed down, go nuts with answers.
Apr 30, 2018 at 19:14 history edited Peter Mortensen CC BY-SA 3.0
Second iteration.
Apr 30, 2018 at 19:09 history edited Peter Mortensen CC BY-SA 3.0
Active reading. [<http://stackoverflow.com/legal/trademark-guidance> (the last section)] - but more work may be needed on the sentence starting with "The people who forget".
Apr 30, 2018 at 9:19 comment added Tschallacka Usually a comment under the question explaining WHY it's a dupe goes a long way, pointing to a certain answer in the dupe target helps too with some guidelines as to how OP can translate it to his problem. Sometimes that helps OP to reword his question to make his problem more specific. But a lot of dupe closes just lack that extra touch.
Apr 30, 2018 at 9:08 comment added PM 2Ring I agree with much of what you're saying (so I upvoted), apart from what you're saying about dupes. OTOH, I certainly agree that much can be done to make dupe closure seem less harsh / hostile to new OPs, and largely that can be done with the existing interface.
Apr 30, 2018 at 8:36 comment added Stargateur "The people who forget that this is a site to help people, to give answers to questions to people can understand, that future visitors can understand on a level that they can understand, to build a knowledge base that's interpretable by advanced coders, and the novices." wow we strongly disagree about that.
Apr 30, 2018 at 8:24 comment added Nathan Tuggy Does anyone really close Java questions as dupes of PHP questions? Seriously?
Apr 30, 2018 at 8:01 comment added Rawling You can welcome and encourage someone while still recognizing that their question is a duplicate and has an answer elsewhere on the site.
Apr 30, 2018 at 7:31 history edited Tschallacka CC BY-SA 3.0
added 13 characters in body
Apr 30, 2018 at 7:21 history answered Tschallacka CC BY-SA 3.0