Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I would like to see a special area of the Monastery where a monk can present a challenge, a place to present and test various strategies and paradigms. Sortof like a Dojo. A hands-on training room.

We could explore timeless questions like, OO, or procedural? I think Perl Monks is the only venue I've seen where this could be handled without a flamewar. We could have some kind of system where a person proposes a challenge in general terms, and then people on both sides can offer some real life scenarios where their techniques excel. Then, both sides can try to implement these things in both, or several, ways, doing Benchmarks as we go, thereby exploring the real advantages and disadvantages involved in each technique. And we can keep a bucket of cold water handy, to dump on anybody carrying a torch.

Other topics could be <BL>

  • XML::Parser, or that Other Way that people are using to get the chatterbox lines?
  • Device drivers in Perl? Why not?! </BL>

    Another nice touch would be have discussion and code sections in the input forms, and run the code input box through Benchmark.

    Paris Sinclair    |    4a75737420416e6f74686572
    pariss@efn.org    |    205065726c204861636b6572
    I wear my Geek Code on my finger.
    

    In reply to Challenges by Aighearach

    Title:
    Use:  <p> text here (a paragraph) </p>
    and:  <code> code here </code>
    to format your post; it's "PerlMonks-approved HTML":



    • Are you posting in the right place? Check out Where do I post X? to know for sure.
    • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
      <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
    • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
    • Want more info? How to link or How to display code and escape characters are good places to start.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Domain Nodelet?
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this?Last hourOther CB clients
    Other Users?
    Others browsing the Monastery: (7)
    As of 2024-04-16 09:34 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      No recent polls found