Or, anywhere: "But why do you want that?"
Context is always useful, though. Because sometimes the person asking has gone down the wrong path and you could help them see the problem from a completely different angle.
Or maybe that context will let you know that yes, they have to use that ancient tech because that's what they have to use at work and no they can't install the latest fancy tech that does it so easily...
"Here is the answer, but why do you want that?" is a tolerable invocation of the X-Y problem.
"But why do you want that?" is derailing. It's an effortless, all-purpose, I'm-so-clever bot post, and it drags a straightforward technical hurdle into some MacGuyver-ass lateral thinking puzzle.
I was once trying to incorporate 2D characters into Blender, with normals. There was no higher goal. That was, itself, the point. But instead I got a bunch of useless advice about how to model my simple example object, and snippy bullshit about doing things properly in 3D. Nobody had a damn thing to say about the discrepancy between the scanline renderer and the path-tracing renderer.
Just use phind.com you will get the relevant references. Chat got but better as it gives the source.
Peple misunderstand “Closed as duplicate” as an insult, when it’s just the hint to look at the provided link. If you didn’t find the answer previously, this just means there are multiple ways to express the problem, which use different words and thus don’t all find the same google result.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
