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, 6 months
2 profile views
Last seen Oct 10 '13 at 15:37
- Stack Overflow 23.9k 23.9k 77 gold badges6565 silver badges127127 bronze badges
- Meta Stack Exchange 1.1k 1.1k 77 silver badges1212 bronze badges
- Super User 972 972 11 gold badge77 silver badges1717 bronze badges
- Mathematics 895 895 88 silver badges2525 bronze badges
- English Language & Usage 847 847 88 silver badges1515 bronze badges
- View network profile →
Top network posts
- 103 ImportError: DLL load failed: %1 is not a valid Win32 application. But the DLL's are there
- 101 Why does pinging 192.168.072 (only 2 dots) return a response from 192.168.0.58?
- 85 auto-detect the phrase "it doesn't work" and ask user if enough info given
- 49 XSL substring and indexOf
- 37 Adding element in middle of xml using xslt
- 33 How do I get Nokogiri to add the right XML encoding?
- 32 Blacklisting resumé liars
- View more network posts →