I don't agree that a behavioral problem can't be, discouraged, for lack of a better term, with technology. Behavior and interface design, which is implemented with technology, are quite inter-related. Design an interface that sucks, and you can pretty well guarantee that users will not use it properly. Even after very carefully designing the system so that it is easy to use it appropriately isn't going to keep some from using it improperly. But, the second interface should provide self-reinforcing feedback (ie, if correct use feels natural, and is rewarding, most people will use it correctly), and thus partially "solve" the behavioral problem.

So, am I bashing PM? No, I'm speaking in generalities. Is there room for PM improvement? Yes. Is the OP's idea something that should be implemented? I'm not qualified to provide a definitive answer.

However I do think the question being asked, and resulting discussion is a good thing for PM. I do hope some sort of interface change can eventually be made such that new users are better encouraged to search first, and ask questions later.

-Scott

In reply to Re^2: 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.