54.4515.984.41.84102
接触 April 29

Code in the Dark 2019 final

暗闇の中の開発

The latest

Posted by Alex Bennett

As usual with code in the dark, some aspect of the competition was not without controversy. On top of our usual technical issues with our chromecasts (something we vow to fix by 2020) we decided this year to change things up for our final, some people found this didn’t quite sit well with what code in the dark is.

In previous years we have had our contestants attempt to animate something using css but of course, coding blind. This has been challenging enough but doing it four years in a row we felt some of our regulars would have css animation syntax memorised and practised to such a degree that new contestants would be unable to compete.

So we changed things up

Our final this year leaned heavily on the third foundational language of frontend development, JavaScript, our contestants we expected to complete the final in 15 minutes, no one managed that. So we gave them an additional 7minutes and 30 seconds, even with this additional time no one managed to solve our problem. Did we make it too hard? Or was it just the environment on the night weighing heavily on our contestant’s ability to concentrate.

We’re going to show what our final challenge was, how we solved it and then how our contestants tried to solve it. To view our final visit here… To download our final click here…. To install it and have it building you will need Node.js installed on your machine along with NPM. Once installed navigate to the final project folder and run npm install. Once this finishes you can run grunt citd to run the project.

3 of out of 5 of our finalists attempted the final, two had a laugh with console logs and dancing badgers, clearly the final was too much of a challenge for them! Here are two potential solutions to this problem. Solution one Solution two

Our winner’s code can be found here…

We enjoyed this year’s event at Duke studios very much. We hope you did too!

Next