The Challenges of Our Contests

The typical response from a Coding Contest participant sounds like:

“Wow, that was an interesting example. It looked so difficult at the beginning, but I managed to finish more levels than I had expected.”

Where do we get the inspiration for our challenges from?

1. Riddles

One source of inspiration are riddles, like in magazines. Actually, the very first example of our Coding Contest in 2007 was to correct a false equation by moving one match.

Try this challenge →

2. Software Projects

Another example was to develop software for grainfield harvesters. The task was to find the path in serpentines or circles with one or more harvesting units.

In serpentines

In circles with 2 units

Try this challenge →

3. Games

A third source of inspiration are casual games like “Unblock Me” where you have to move wooden bars in order to allow the red bar to freely move to the right (see the video). The programmatic solution was to solve arbitrarily difficult configurations that would be too hard to solve manually.

5.3 UnblockMe
Try this challenge →

How to to fit those examples into a 4 hours contest?

Naturally, all challenges have a different level of inherent complexity. To adapt them for our contests, we break them down into levels of increasing difficulty: almost everybody should be able to finish the first level; many should be able to finish the second, fewer the third level, etc. The following diagram visualizes the percentage of participants who finished which level.

5.3 Chart

Participate on 2017-10-20 →

 

The light blue curve depicts a challenge that was quite tough (nobody finished level 5) while the red curve shows a challenge where much more people were able to solve the levels 4, 5, and 6.

When preparing a challenge, we usually have internal test runs to check how well a new example fits into that set of curves. If it’s too difficult, we split levels apart or add some hints. If it’s too easy, we collapse levels, increase the data set, etc.
Typically, we try to make level 5, 6, and 7 quite selective, such that even the best coders have a hard time solving them.

How to tell whether a solution is correct?

For many examples, it is easy to tell whether a solution is correct, e.g. for the “move one match” challenge from above:

Wrong Equation Corrected Equation
3 = 2 2 = 2 or 3 = 3
93 + 27 – 30 + 16 = 68 53 + 27 – 30 + 18 = 68

For other examples it may be much harder, e.g. with “Autonomous Cars” from 2014 where the task was to “drive a distance of 10 kilometers; avoid speeding tickets; avoid tickets for reckless driving; finish the test drive in under 690 seconds; keep the total energy usage below 6100 Wh”. For such examples we typically develop a simulator with a programmatic and a visual interface. The solutions of the participants then have to interface with the simulator which verifies the driving commands and gives feedback (see the blog article).

How long are the solutions (in lines of code)?

The honest answer is: “It depends.” Here is one concrete example:

Level Lines of Code (Java)
Level 1 53 lines
Level 2 59 lines
Level 3 77 lines
Level 4 80 lines
Level 5 99 lines
Level 6 112 lines

Since we allow any programming language, those lines may differ a lot. Some problems are easier to solve in some languages. However, over the years we’ve seen that most often the best coders choose common programming languages like Java, Python, C++ or C# (e.g. see Infographic). Those are all imperative languages with similar language constructs, so the length of the solution depends more on the creativity of the coder than on the programming language.

The next Coding Contest is on 2017-10-20 and will take place in many locations in Europe and South Africa.

Register →

 

Seats are limited — register now!

 

About the Organizer

The global organizer of the international Coding Contest, Catalysts, creates the challenges and selects the locations where the Coding Contest takes place.

This article was initially released by Catalysts in a blog series called „The Catalysts Way“. Read the full chapter about what’s behind the Coding Contests here:

Read the whole chapter „Coding Contests“ →

 

Hinterlasse einen Kommentar

*wird nicht veröffentlicht