in reply to Re^6: using the power of consideration responsibly (what is personal attack what is trolling, can you lose power to consider)
in thread using the power of consideration responsibly (what is personal attack what is trolling, can you lose power to consider)

I am not saying the consideration system if fail-proof, but I still prefer having it over not having it or revoking consideration powers from *some* by a decision of gods or handing reaping powers only to a select *few*.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics
  • Comment on Re^7: using the power of consideration responsibly (what is personal attack what is trolling, can you lose power to consider)

Replies are listed 'Best First'.
Re^8: using the power of consideration responsibly (what is personal attack what is trolling, can you lose power to consider)
by Anonymous Monk on Jun 08, 2013 at 10:59 UTC

    I am not saying the consideration system if fail-proof, but I still prefer having it over not having it or revoking consideration powers from *some* by a decision of gods or handing reaping powers only to a select *few*.

    Remember /borg ? There is no reason for the losing of power to consider to be permanent

      Borging is an answer to an entirely different issue. And it is used very very sparingly.

      Since the consideration system is not broken, or not even considered a problem by the Monastery, I tend to go by the "Don't repair it, if it ain't broken" maxim.

      Allow me to ask you a more personal question: you seem genuinely interested in the good working of the Monastery. Why don't you join us and post under your own identity?

      CountZero

      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

      My blog: Imperial Deltronics

        Borging is an answer to an entirely different issue. And it is used very very sparingly.

        I understand, I used it as an example of an existing policy with a feature of time limit which is why I mention of time limit being an option that could be considered :)

        Since the consideration system is not broken, or not even considered a problem by the Monastery, I tend to go by the "Don't repair it, if it ain't broken" maxim.

        I understand your position

        Allow me to ask you a more personal question: you seem genuinely interested in the good working of the Monastery. Why don't you join us and post under your own identity?

        Been there, done that, still doing it :) I am Anonymous Monk :)