@soniaprevost] and @atmosfeer, Le Wagon alumni Batch #6 and Batch #8 respectively, started the idea of not so friendly coding wars between batches :) Here are the rules for epic nights:
You do NOT talk about Fight Night.
You do NOT talk about Fight Night.
Two teams battle against each other. There can be as many coders on each team as desired, as long as they're from the same batch.
The officiating crew consists of one main referee and two side-judges, one from each batch competing. The side-judge's role is to observe the opposing team and make sure that rules are being respected.
5 rounds of increasing difficulty. One code kata will be solved each round by each team. The first team to win 3 rounds wins the battle. Each round has a duration pre-determined by the referee depending on the kata.
Code Katas (in Ruby) are selected prior to the fight by an impartial referee, one for each round. The katas in question are secret to the teams before the event, obviously.
Teams shall be separated in different rooms during the battle to keep copycats honest.
Each team can use one laptop for coding and two laptops for research. The only resource allowed is the Ruby Doc. No Google, no Stack Overflow, and no outside help . Have a cookie and go cry about it in the corner.
All phones from the members of both team will be gathered by the officiating crew to ensure no outside help is provided.
Points will only be attributed each round if the code runs all the tests successfully. No cumulative score will be considered, only numbers of rounds won. The score for each round shall be calculated using the following formula:
round_length = amount of time for the given round in seconds time_spent = time spent in seconds by the team to solve the kata before the final submission. run_time = time in milliseconds to execute all the tests successfully. code_elegance = a mark given by the ref. See rule 10 for details
score = (round_length - time_spent) + ( (1000 - run_time) * 3 ) + (300 * code_elegance)
After each round, the ref will take a look at each solution and give a mark from 1-10 based on the following criteria:
- cleverness & efficiency of answer
- elegance & legibility of code
- whether the answer follows Ruby & general best practice