We, obviously, do not want to reinvent the wheel over and over again.
So, how to ask such questions, that by definition cannot have the
What you are talking about is not a "question," it is a "discussion point."
If a question has no right answer there are three possibilities:
- It is impossible to know (e.g. what is on the other side of an event horizon?)
- It is possible to know, but we do not have an answer yet (e.g. P == NP?)
- It is soliciting opinions.
The first two can work as questions. History is littered with research papers that explore topics with the result "nope, that doesn't work -- yet." But you asked about "by definition" not having a right answer, which fits squarely into condition three, which would be "primarily opinion-based," a close reason everywhere on Stack Exchange.
My question is about questions that asks users to share their
experience and/or offer creative suggestions in solving/approaching a
Sharing experiences works in a forum (this is not a forum) or in chat. Not in the Q&A format.
However, the "particular problem" part is probably on-topic if asked right. Questions should be about programming problems and soliciting creative solutions to solve them.
Presenting a design and asking for feedback is fine, as long as it is properly-scoped and not too broad. That is not really what you were getting at, but it is a better focus for those types of questions.