9

Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, and why they didn't work.

"why they didn't work".

That's a stupid phrase. You don't know why it didn't work. How about "and what error you got" or "and what you expected to happen".

If folks knew why it didn't work, 90% of them wouldn't come here.

7
  • 3
    While I believe that most people don't take that phrase literally - understanding full well that "why" actually means "specifically how" - I'd love to know what objection the down-voters have against making this phrase less ambiguous.
    – Aaron Bertrand Staff
    Commented Jan 8, 2014 at 19:20
  • 3
    You're talking about developers. We're often a pedantic lot. :p (really doesn't make us right, just pedantic)
    – jcolebrand
    Commented Jan 8, 2014 at 19:21
  • 3
    Not as pedantic as DBAs.
    – Aaron Bertrand Staff
    Commented Jan 8, 2014 at 19:22
  • 2
    May not worth the effort to change this. Shog has stated that this close reason will be going away, presumably in favor of something worded a lot better with less overlap Commented Jan 8, 2014 at 19:30
  • @psubsee2003 ah very cool, was not aware of that one.
    – Aaron Bertrand Staff
    Commented Jan 8, 2014 at 19:34
  • 2
    @AaronBertrand My DBA isn't pedantic at all... But my sample size of 1 probably isn't reliable.
    – Cruncher
    Commented Jan 8, 2014 at 21:25
  • @Cruncher considering he's a dba.se mod, he's probably making a private joke ;-)
    – jcolebrand
    Commented Jan 9, 2014 at 7:31

0

Browse other questions tagged .