I think we are, for the most part, in agreement; but talking past one another. Technology can not fix behavioral problems, if someone doesn't want to search, even doing the search for them isn't going to get them to stop and read what the search found. I agree with that.

And I understand the desire to not put unnecessary strain on a system by doing what would largely be futile searches. I'm not an advocate for the OP's original idea, but I'm willing to entertain weird ideas for the sake of finding something that would work.

What I did say was that the user interface presented by PM has room for improvement, and that the interface could do a better job encouraging people to search for answers before posting their questions.

So, the basic tenet I'm presenting is that while technology can't fix behavioral problems, it can, through the use of good user interfaces, encourage correct behavior. The XP system here is simply one way technology is used to encourage correct behavior. While not perfect, it can certainly be said to be mostly successful.

I'll add some more comments about possible improvements I've thought about in a different node.

-Scott

In reply to Re^4: New node - Supersearch - Feature proposal ! by 5mi11er
in thread New node - Supersearch - Feature proposal ! by prad_intel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.