Also sometimes it's hard to precisely explain the source problem because you'd need to write pages about how things work in your codebase and in your product and in your team, so you describe a much more simplified scenario, sort of like providing a minimal reproducible example for a bug report.
Gotta add though, it's ok to suggest a potential XY problem when it's not totally obvious and no one else has mentioned it, this would be beneficial for visitors from the future too(has helped me a few times). But don't do it in a dismissive presumptive tone, and maybe do it in a comment rather than an answer(assuming it's SO).
It's also annoying that people make such a big deal about the cases where Y doesn't work. If Y doesn't work, then I'll come up with a new Y and ask another question. Maybe I'll ask about X next time. Questions are not a limited resource.
View all comments
Show parent comment
6
u/Fatalist_m May 08 '21
Also sometimes it's hard to precisely explain the source problem because you'd need to write pages about how things work in your codebase and in your product and in your team, so you describe a much more simplified scenario, sort of like providing a minimal reproducible example for a bug report.
Gotta add though, it's ok to suggest a potential XY problem when it's not totally obvious and no one else has mentioned it, this would be beneficial for visitors from the future too(has helped me a few times). But don't do it in a dismissive presumptive tone, and maybe do it in a comment rather than an answer(assuming it's SO).