If a good survey was conducted and showed that a supermajority of Monks want, in general, such minor improvements to be made to old nodes, then you'd have a much better argument.

Good surveys are rather difficult to produce because it is much too easy to bias the results quite a bit based on minor changes in how you word the questions.

Even with a good, objective survey, I find an open debate much more compelling. It is too easy to click "Answer A" without really thinking through the issue. I'm much more persuaded by someone presenting why they would choose "Answer A" and with how others react to such declarations.

So (to take an extreme position which seems terribly unlikely) even if 90% of monks want "A" but 5% of monks want "B" and several of those 5% write eloquently about why "B" is a Good Thing while only a very few relatively poorly received replies try to refute any of their points or to defend "A" (some of which are eloquently refuted) and the "B" nodes even get quite a few more upvotes than "A" nodes (some of which get just a few downvotes)...

...then you could hire the world's best survey team and convince me that 90% of monks want "A" and I'm pretty sure I'd advocate "B".

I want to do what is best for the site, even if that isn't the most popular choice.

And voting on considerations is a quite bad form of survey. The consensus and policy is that having 2/3 of votes "for" a consideration is just not much support. Such a vote often means that there will be an outcry if the consideration action is implemented and yet will be less grumpling when the action is reversed.

I want to know what principles are well-regarded here and use them to guide action. And those easily beat a straw poll about a specific action, especially when the principle calls for not changing something.

- tye        


In reply to Re^2: Should janitors add links to posts? (poll < principle) by tye
in thread Should janitors add links to posts? by davido

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.