Reviewing code is fun! Use this tag to identify your post as an entry to the current community challenge. See the Community Bulletin, or browse the CR Meta site for more info. Typically you should also tag community-challenge questions with [tag:game] as well.

Related tag:

It all started with a small group of CR addicts that were discussing questions in The 2nd Monitor (the site's main chatroom), when a monkey proposed the idea:

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.

And so the tag was born. We grew fond of it, and for several weeks in a row a new challenge was being voted upon.

That was December 2013.

is slightly different. Participants have an entire month to submit entries, and while the first challenge was also decided in chat, subsequent ones will be voted upon by the community, on the meta site.

The has now been made a synonym of the more general .

Over time the concept may evolve and that is a 'good thing'™


About :

Why? For the heck of it.

Who? Everyone that thinks they can wants to implement the challenge with the best code they can write.

What? That's agreed upon by the community (that's YOU!) voting on the meta site.

How? That's the beauty of it. Sky's the limit. Some take it literally.

When? Pay attention to the Community Bulletin when you pay us a visit:

CB

Late entries will be downvoted to oblivion Entries can be submitted anytime, but we'd prefer this being a timely event, be it only to measure and correlate the site's metrics:

CR Activity Graph, April 2011 - January 2014

https://data.stackexchange.com/codereview/query/161411/site-activity-and-votegraph#graph


FAQ.

Q. Code Golf & Programming Puzzles Stack Exchange has a tag. Isn't this overlapping?

A. No. This comment is very good at explaining why:

@BenVoigt The first two 'on-topic' requirements for PCG are An objective primary winning criterion, so that it is possible to indisputably decide which entry should win. and A clear specification of what constitutes a correct submission. Test cases are highly encouraged.

These two requirements are expressly avoided for our challenges. We have no winners, and we have no specific 'correct submission'. – rolfl 7 hours ago


Q. Why is every challenge a ?

A. Simply because coding a small game is fun, and if you were asked to come up with a project idea that you could implement and post for peer review in a single weekend, you'd probably think of ...a small game. That's all there is to it. Nothing prohibits proposing something different, the idea with the most votes at the end of the voting period becomes the current .


Q. So everyone codes the same thing. Aren't these posts likely to be duplicates?

A. *There are as many ways to implement a solution in one language, as there are programmers implementing the solution in that language**. There is no language constraint whatsoever; these code review challenges can be an opportunity to fiddle with a new language and IDE (although they're not likely to be as easy as the average "Hello, World!").


Q. I code crap, I'm scared.

A. You're not alone.

You're not alone

This is why you're here: to share some real working code you've written and would like to get peer reviewed. Don't be scared, nobody bites. Not even the monkeys. You're here to learn - we all are. If you're a beginner and would like to tell the community to be more... gentle and understanding about the mess you've put yourself into, don't hesitate to stick a tag on your post.

history | excerpt history