Return to Question

Those of you that weren't following what's going on in the chat room might have been taken by surprise by a recent avalanche of Rock Paper Scissors Lizard Spock posts.

This is how it started:

OK, weekend challenge.... we all solve the Rock Paper Scissors Lizzard Spock problem with our 'favourite' language, and we all have to post a question here with our solution to be reviewed.

 

http://chat.stackexchange.com/transcript/message/12408541#12408541

If this is a good idea, then I think we have something like an amazing idea waiting to be exploited: Each weekend challenge can be discussed in one of our lovely chat rooms, normally The 2nd monitor.

The per-round output zombie-hunting mission is slowing down; until Winter Bash 2013 starts, there's still a couple of weeks. Just because it's fun, I suggest we create a weekend-challenge tag that people could follow (or ignore), and for the next couple weeks, we decide on a little project to submit review requests for.

###Rules

• The project must be a small (tiny!) project that can be completed within a couple of hours.
• There is no language constraint, participants can implement the project in any language they like.
• The project scope should be vague enough for participants to implement it as ["simply" | "cleverly crafted"] as they can/like; the only constraint is that the project must solve the given problem.
• Avoid the get-it-done-fast trap, and post your best possible code! This isn't a race for the first post We want quality posts!
• If you are late in submitting your solution, we will hunt you down and That's perfectly OK. We really can't prevent anyone from submitting code to any solution. Just because it's not the "active weekly challenge" doesn't make it off-topic, as long as you write a question that fits what the site is about.
• Entries must be tagged with weekend-challenge, along with the tag of the language you're coding your weekend challenge entry with (, and any other applicable tags).

###How it works

Each week a new meta-question will be posted on this site; the community submits ideas as answers to that question (1 idea per answer), and the highest upvoted answer on the Saturday (12AM UTC) of that week, becomes that weekend's challenge.

Each week the meta-question containing the proposals, will be posted here as an answer, with a link.

Those of you that weren't following what's going on in the chat room might have been taken by surprise by a recent avalanche of Rock Paper Scissors Lizard Spock posts.

This is how it started:

OK, weekend challenge.... we all solve the Rock Paper Scissors Lizzard Spock problem with our 'favourite' language, and we all have to post a question here with our solution to be reviewed.

http://chat.stackexchange.com/transcript/message/12408541#12408541

If this is a good idea, then I think we have something like an amazing idea waiting to be exploited: Each weekend challenge can be discussed in one of our lovely chat rooms, normally The 2nd monitor.

The per-round output zombie-hunting mission is slowing down; until Winter Bash 2013 starts, there's still a couple of weeks. Just because it's fun, I suggest we create a weekend-challenge tag that people could follow (or ignore), and for the next couple weeks, we decide on a little project to submit review requests for.

Rules

• The project must be a small (tiny!) project that can be completed within a couple of hours.
• There is no language constraint, participants can implement the project in any language they like.
• The project scope should be vague enough for participants to implement it as ["simply" | "cleverly crafted"] as they can/like; the only constraint is that the project must solve the given problem.
• Avoid the get-it-done-fast trap, and post your best possible code! This isn't a race for the first post We want quality posts!
• If you are late in submitting your solution, we will hunt you down and That's perfectly OK. We really can't prevent anyone from submitting code to any solution. Just because it's not the "active weekly challenge" doesn't make it off-topic, as long as you write a question that fits what the site is about.
• Entries must be tagged with weekend-challenge, along with the tag of the language you're coding your weekend challenge entry with (, and any other applicable tags).

How it works

Each week a new meta-question will be posted on this site; the community submits ideas as answers to that question (1 idea per answer), and the highest upvoted answer on the Saturday (12AM UTC) of that week, becomes that weekend's challenge.

Each week the meta-question containing the proposals, will be posted here as an answer, with a link.

Those of you that weren't following what's going on in the chat room might have been taken by surprise by a recent avalanche of Rock Paper Scissors Lizard Spock posts.

This is how it started:

OK, weekend challenge.... we all solve the Rock Paper Scissors Lizzard Spock problem with our 'favourite' language, and we all have to post a question here with our solution to be reviewed.

http://chat.stackexchange.com/transcript/message/12408541#12408541

If this is a good idea, then I think we have something like an amazing idea waiting to be exploited: Each weekend challenge can be discussed in one of our lovely chat rooms, normally The 2nd monitor.

The per-round output zombie-hunting mission is slowing down; until Winter Bash 2013 starts, there's still a couple of weeks. Just because it's fun, I suggest we create a weekend-challenge tag that people could follow (or ignore), and for the next couple weeks, we decide on a little project to submit review requests for.

###Rules

• The project must be a small (tiny!) project that can be completed within a couple of hours.
• There is no language constraint, participants can implement the project in any language they like.
• The project scope should be vague enough for participants to implement it as ["simply" | "cleverly crafted"] as they can/like; the only constraint is that the project must solve the given problem.
• Avoid the get-it-done-fast trap, and post your best possible code! This isn't a race for the first post We want quality posts!
• If you are late in submitting your solution, we will hunt you down and That's perfectly OK. We really can't prevent anyone from submitting code to any solution. Just because it's not the "active weekly challenge" doesn't make it off-topic, as long as you write a question that fits what the site is about.
• Entries must be tagged with weekend-challenge, along with the tag of the language you're coding your weekend challenge entry with (, and any other applicable tags).

###How it works

Each week a new meta-question will be posted on this site; the community submits ideas as answers to that question (1 idea per answer), and the highest upvoted answer on the Saturday (12AM UTC) of that week, becomes that weekend's challenge.

Each week the meta-question containing the proposals, will be posted here as an answer, with a link.

Those of you that weren't following what's going on in the chat room might have been taken by surprise by a recent avalanche of Rock Paper Scissors Lizard Spock posts.

This is how it started:

OK, weekend challenge.... we all solve the Rock Paper Scissors Lizzard Spock problem with our 'favourite' language, and we all have to post a question here with our solution to be reviewed.

http://chat.stackexchange.com/transcript/message/12408541#12408541

If this is a good idea, then I think we have something like an amazing idea waiting to be exploited: Each weekend challenge can be discussed in one of our lovely chat rooms, normally The 2nd monitor.

The per-round output zombie-hunting mission is slowing down; until Winter Bash 2013 starts, there's still a couple of weeks. Just because it's fun, I suggest we create a weekend-challenge tag that people could follow (or ignore), and for the next couple weeks, we decide on a little project to submit review requests for.

###Rules

• The project must be a small (tiny!) project that can be completed within a couple of hours.
• There is no language constraint, participants can implement the project in any language they like.
• The project scope should be vague enough for participants to implement it as ["simply" | "cleverly crafted"] as they can/like; the only constraint is that the project must solve the given problem.
• Avoid the get-it-done-fast trap, and post your best possible code! This isn't a race for the first post We want quality posts!
• If you are late in submitting your solution, we will hunt you down and That's perfectly OK. We really can't prevent anyone from submitting code to any solution. Just because it's not the "active weekly challenge" doesn't make it off-topic, as long as you write a question that fits what the site is about.
• Entries must be tagged with weekend-challenge, along with the tag of the language you're coding your weekend challenge entry with (, and any other applicable tags).

###How it works

Each week a new meta-question will be posted on this site; the community submits ideas as answers to that question (1 idea per answer), and the highest upvoted answer on the Saturday (12AM UTC) of that week, becomes that weekend's challenge.

Each week the meta-question containing the proposals, will be posted here as an answer, with a link.