WDYEWDYG? "What did you expect, and what did you get?" Question-askers often say something "doesn't work" but forget to tell what it actually does, what they expected it to do, or both. Often, the problem is in a mistaken expectation of what should happen, or a mistaken interpretation of what did happen.
In order to help them, one has to make assumptions and guess at these things, and the guesses may be off-target, resulting in an annoying waste of time for both sides.
It's like Nebuchadnezzar asking for an interpretation of his dream but refusing to reveal the dream itself. I'm looking for effective ways to remind people. There are wonderful articles on how to write a good question, but a huge class of people will not find and read such an article. Any ideas?
My work: Android apps and GIS mapping for a non-profit org.
Less often: ConTeXt, C.
Member for 8 years, 7 months
1 profile view
Last seen Jun 24 '16 at 18:53
Top network posts
- 100 Why does pinging 192.168.072 (only 2 dots) return a response from 192.168.0.58?
- 96 ImportError: DLL load failed: %1 is not a valid Win32 application. But the DLL's are there
- 84 auto-detect the phrase "it doesn't work" and ask user if enough info given
- 45 XSL substring and indexOf
- 35 Adding element in middle of xml using xslt
- 31 How do I get Nokogiri to add the right XML encoding?
- 31 how to build an APK and separate libraries that the app loads dynamically
- View more network posts →