There are 16 days left before the beginning of the next contest Hypersonic. We will celebrate the second anniversary* of the platform and we’re really excited to share it with you. We hope you’re ready!
Day minus 117, Conception
Romain, Art Director: “It’s a girl, we need to find her a name”
|Romain working on the main illustration|
|Contest name: results of the vote|
All of this should be done really early. Indeed at the end of a contest, the registration page of the next one should be updated. So everything needs to be ready at the end of Codebusters.
Day minus 85, Hacking
Alexis, Corporate Relations Hacker: “Hey, the contest has to be crazy good, because another company is ready to work with us”
Some developers register for fun and glory. Others want to get noticed by companies. Our goal is thus to showcase lots of interesting job opportunities to them.
Day minus 54, Brainstorm
The whole dev team:
“_ We could do a game like StarCraft?
_ Too complex.
_ Something chess-like ?
_ Too classic.
_ A game with bluff like poker?
_ Too random
|Background of the game|
Day minus 50, Building
Julien, Game Builder: “The status for Hypersonic, well, it’s ongoing.”
Each game is mainly built by one developer only. Of course, all the team can help for anything: testing, code review…
|Asset of the game|
Day minus 36, Testing
Jerome, Product Manager: “Yeees, I beat the boss”
Follows a series of iterations between the game builder and the testers. Usually all developers try the game and give some feedback. Rules are tweaked, the statement is improved, art assets are added to the game…
Day minus 24, Promotion
Thibaud, community manager: “Already 5 CodingHubs!”
The more, the merrier. A contest is a programming competition, but it’s also a fun event where a lot of developers discuss and share their passion for coding. For example, in a CodingHub.
Hour minus 1, Excitation
It will seem like a normal day at work although it’ll be Saturday afternoon. Most of the team will gather to ensure a smooth launch of the contest.