5 ms·
Real conversation I've had: "Does Django's query builder use prepared statements by default?" "What are you really trying to do?" "I'm trying to find out if
by Can_Not 7y ago
Real conversation I've had:
"Does Django's query builder use prepared statements by default?"
"What are you really trying to do?"
"I'm trying to find out if Django's query builder uses prepared statements by default..."
Not everything is an XY problem. If somebody found that question on SO via Google, they would be pretty annoyed to see it XY'd instead of answered.
- oconnor663 7y agoYeah as a courtesy, if X is easy to answer, it's better to answer it and then ask about Y.
- agumonkey 7y agoThat's probably a highly efficient way to get booted of most IRC channels.
- deleted 7y ago[deleted]
- raverbashing 7y agoWhat happens sometimes is that X is supposed to be simple but it doesn't work or it doesn't work for that specific case, so you're trying to work around it by doing Y (or Z, etc.)
- emilfihlman 7y agoYou are in the small, small, minority. It's extremely bad to not take the XY-problem seriously because you think it doesn't apply to you.
- davidivadavid 7y agoThat's definitely a case where asking that question wasn't warranted. You asked a question about a factual thing. It's essentially a yes/no answer, not a "how to" answer, which are way more prone to the XY problem.