• You have to give a certain amount of trust to your peers or you take away the fun factor.
    I agree that people will need to have patience and restrain themselves from checking what others think. But it is human nature to be curious and people will be tempted to check what others think of their programming (skilz). I know I will be tempted, but I will just have to put a filter in my proxy server to stop myself from accessing the Thread!
  • I am not proposing that this require any modification to the way the Monastery works now.
    Clear. This would take up much time and if we assume that people won't check ;-) there will be no need for an adaptation...
  • I will personally be responsible for notifying all the authors
    Good! So should there be a deadline before which the first post needs to be created? Or will you just parse the start-time from the node's creation time? That would be the most simple task. You could parse it if people will start their time-lock node with a specific subject. (eg: TimeLock: Level1 - Limbic~Region). This could even be one of the little projects.. (yours??)
  • Part of the fun is comparing yourself to others
    So very true (see Obfuscated Code or Code Catacombs). So yes, lets stick to having a couple of different catagories where people of the same skillset can enter their code and compare how they 'evolved' compared to their skill level compadres!

    I hope that many people will actually make these little programs. Looking back at code I wrote 3 months ago, there are already many improvements I would like to make! So how long would you suggest for a waiting period?? 6 months, 1 year, more?? I would say 6 months at least.

    .:| If it can't be fixed .. Don't break it |:.

    In reply to Re^3: Solicitation Of Ideas For "Time Capsule" Project by aukjan
    in thread Solicitation Of Ideas For "Time Capsule" Project by Limbic~Region

    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.