Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Another consideration on considering

by robartes (Priest)
on Oct 24, 2002 at 19:42 UTC ( [id://207831] : monkdiscuss . print w/replies, xml ) Need Help??

Having recently booboo'd by considering a node for deletion that in hindsight should not have been considered (see On Responsible Considerations as to why I feel I should not have - it was OT, which is no reason to consider stuff for deletion), I'd like to rehash the subject of consideration a bit.

As the above mentioned node, and many others touching on consideration, rightly state, consideration can lead to nodes getting reaped, which is a very serious thing. I sure would not like seeing one of my nodes vanishing in a puff of smoke, especially if I'm a new and inexperienced monk still getting my feel for the monastery, and I don't think anybody will disagree with me. Consideration is a serious thing indeed.

Unfortunately, I only read On Responsible Considerations after I had considered a node for deletion, which is of course too late. This leads me to my point: is it technically possible to somehow force a "first time considerer" to read that node before considering any nodes? And what is the monks feeling about the desirability of such a contraption?

Okay, one can make the point that when a monk reaches friarhood, (s)he should have enough of a feel for the procedures and culture of the monastery to act responsibly and look for information on this kind of thing before using it, and that certainly is a valid point. However, it is easy to miss information, be it through laziness or just through the overwhelming amount of info that is available (something to do with a forest and trees). I know that in my case, I did some searching around on consideration and found some nodes on the various shapes and colours of the beast and how to use it responsibly, but as I said, I only came across On Responsible Considerations too late.

Then again, having to read a node and click on some button before doing an action might quickly degenerate into the usual "EULA acceptance" behavior: click without reading. I dunno. Any opinions?

Robartes- keeping his fingers off the consider button for a while

Replies are listed 'Best First'.
Re: Another consideration on considering
by greenFox (Vicar) on Oct 25, 2002 at 01:20 UTC
    Don't worry it is also OK to make mistakes around here, it happens to every-one. I am sure no great harm was done. If you really need to get it off your chest you can always visit the Confession Booth, its good for your immortal perl soul :)

    Life is a tale told by an idiot -- full of sound and fury, signifying nothing. William Shakespeare, Macbeth

Re: Another consideration on considering
by rdfield (Priest) on Oct 25, 2002 at 09:19 UTC
    Maybe a list of nodes to read each time a new level is reached would be good to have. The XP nodelet would be the obvious place:
    "You have gained 2 XP, you have 499 points before level 7, please read On Responsible Considerations and ...insert other Friar related nodes here...".


      You can visit this node for a summary of each level's powers. Within the description of powers for a certain level is also recommended reading for using those powers. I know it's helped me when I've hit the next level.


      Perl6 Grammar Student

      Interesting idea... The problem is that you (or at least, I) can wind up missing changes like that in the XP nodelet, if you're clicking talk to send to the chatterbox, or you're previewing/posting a node, for instance.

      I think the original suggestion was pretty good. If you haven't considered before (or even possibly frontpaged?), getting diverted to a page that refers to On Responsible Considerations or How do I moderate? (or Am I a power-mad Friar? :)) would not be a bad thing...

      All we need now is to get a pmdev interested.

        I imagine it would be relatively difficult to fit into the XP nodelet code, where it doesn't really belong. A simple solution that addresses the elusiveness of the XP nodelet messages that should also be much easier to add somewhere: when you reach 490 XP, you get a root /msg saying something along the lines of the text that was proposed. That will probably also attract more attention, ie not be so prone to conditioned click-through-EULA reactions.

        Makeshifts last the longest.