News for hackers. Stuff that matters.
Re:Evidence-Based Guidelines for Writing Questions on Stack ... by lostlogin on Thursday December 28, 2017 @03:56AM (#16021038)
Flagged as duplicate.

Hasn’t happened to me, but nothing is more frustrating that having someone else ask my exact question then it gets flagged.

Re:Evidence-Based Guidelines for Writing Questions on Stack ... by foepys on Thursday December 28, 2017 @04:33AM (#16021130)
I often reach assumed duplicates via Google but still get very insightful answers. If I click on the link pointing towards the assumed original, it's sometimes completely deserted with a single two-line answer that's been outdated for three years.
Re:Evidence-Based Guidelines for Writing Questions on Stack ... by menacingly on Thursday December 28, 2017 @08:39AM (#16021911)
And they're happy to leave the duplicate up for the inbound google benefits it provides.
Re:Evidence-Based Guidelines for Writing Questions on Stack ... by katastic on Thursday December 28, 2017 @04:30AM (#16021120)
And then the duplicate doesn't even have the answers you need.
Re:Evidence-Based Guidelines for Writing Questions on Stack ... by cpburns2009 on Thursday December 28, 2017 @10:44AM (#16022584)
The best part is when the duplicate is related to your question, but the duplicate question is structured differently so you don't know how to apply its answers to your question. Sure, if you already knew the answer the duplicate answers make sense, but without that knowledge (hence why you asked in the first place) they are completely unhelpful.
Re:Evidence-Based Guidelines for Writing Questions on Stack ... by mark-r on Thursday December 28, 2017 @01:21PM (#16023755)
If the duplicate doesn't answer your question, you're supposed to edit your own question to indicate why the linked question wasn't helpful. At that point you're supposed to magically attract enough attention to get the question reopened. Unfortunately it rarely works out that way.