|The stupid question is the question not asked|
That is, does the statement,
I have an idea that might be of use to you in solving your problem, but I am unsure of enough of the detail to offer an implementation or even to know if the idea has any real possibility of working.
have any merit either to the OP of the problem, or to perlmonks as a whole?
Occasionally, I see a question here, that despite being beyond my knowledge base (eg. unix), I think I see a possibility for an easier or better solution than those already presented. I am unable to supply a tested answer, and am not in a position to know if the idea has merit in the target environment as there are inevitably sufficient differences in implementation details cross-systems, even when the concepts themselves are generic.
What should I do?
A[ ] B[ ] C[ ] D[ ]?
Cut&paste, check a box as an answer will do, if discussion would be too difficult. Anonymonk can answer as many times as s/he likes.
Personally, if I am really stuck on a problem--stuck enough that I feel the need to post a question here or elsewhere--whilst I am more than happy to receive a fully authorative, worked solution. In it's absence, I am also happy to receive a speculative possibility for one. Although these can lead me to expend effort that is notionally wasted, if the idea doesn't pan out, I still value it because sometimes the fresh perspective/approach to a solution can cause me to think different and arrive at a solution that I might otherwise never have thought of. Besides, sometimes they pan out and I'm a happy bunny.
Am I alone in thinking this way?
If this prompts enough people to answer, for me to draw a consensus or majority community opinion, I will base my future action when these speculative ideas pop into my head on that, explicit or perceived, consensus.
Examine what is said, not who speaks.
The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.