Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I like the idea and the less work I would have to do to make it happen the better. This means that your ideas for contests are key. Ideally if someone else (possibly the one who suggested the contest) graded/scored them that would be great.
    I see several different types of contests
  • Game oriented: Tournament type of setup for scoring. I think of nate and my AI class where we had to do that sort of thing with kalah. Each player could have a class which had a selectMove method. A game controller would then keep track of board position,score, and check validity of moves.
  • Level of correctness. Given a problem which program outputs the most correct answers. Benchmark them to break ties.
  • Subjective: ie Obfuscated Code or Perl Poetry.... which one is coolest? Regular voting would probably work... although we'd probably want to limit the time which people could vote on code... possibly how many votes a user got for a given contest... we would probably also want to hide the identity of the author of the code.
  • Perl Golf: shortest code that solves a particular problem wins
Then there are just the questions of how code is submitted? Who can see submissions and when? How does scoring work for a particular contest?

vroom | Tim Vroom | vroom@cs.hope.edu

In reply to RE: Some contests? by vroom
in thread Some contests? by Rydor

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 meditating upon the Monastery: (6)
As of 2024-04-19 12:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found