Skip to content

Latest commit

 

History

History
43 lines (22 loc) · 2.33 KB

README.md

File metadata and controls

43 lines (22 loc) · 2.33 KB

Welcome to the I TAKE Unconference 2015 Contest!

About the Contest

The best reward for a software craftsman is to learn new things. Mozaic Works, the I TAKE Unconference organizers, want to create this opportunity for you every year. This contest is a set of challenges that will put your skills to the test. Do you know how to test systems? Can you point coding issues? Are you open to learning from other people? And, best of all, can you safely clean up existing code and improve its design? These are all core developer skills nowadays, and you'll greatly benefit from mastering them. This is just one opportunity to do so.

We hope that you will enjoy this contest. Oh, we almost forgot: the person who gathers the most points wins a gadget. That's a small reward compared to the learning, but we're sure it helps :).

Enjoy!

How it Works

All you have to do to register is to fork this repository. You will need a github account for your real name. Once you've finished a challenge, make a pull request with a comment stating the challenge number.

If you want to improve a solution you've already submitted, just make another pull request with the same title. For each of the challenges, the jury will take into account the last pull request before the deadline.

You have time until May 29, 2 pm. Any pull request done after the deadline will be discarded by the jury.

Challenges

Show your craftsman skills in a set of short challenges and gather up to 100 points. The person with most points wins a gadget.

1. For 10 points: Tweet to @itakeunconf a photo with you pair programming with another attendee at the conference with the hashtag #itakecontest.

You get the points if we can see both of you on a keyboard in front of a screen with code on it.

Read the full instructions in the challenge-1/problem.txt file.

2. For max 20 points: Write all the test names you would write

Read the full instructions in the challenge-2/problem.txt file.

3. For max 20 points: Describe briefly all the bugs you find in this code

Read the full instructions in the challenge-3/problem.txt file.

4. For max 20 points: Review this code and write down all the code smells you found

Read the full instructions in the challenge-4/problem.txt file.

5. For max 30 points: Refactor this code.

Read the full instructions in the challenge-5/problem.txt file.