During June 9th and 10th, Our company, who paid a great attention to the EOS Marathon Contest in Hong Kong, sent 4 very capable man (it may be self-praise) to participate. Deeply touched during this contest, we found that the blockchain developers from all over the world were still quite enthusiastic about the EOS, and learned that it also required more imagination to take part in such activities.
### More than 70 teams, hundreds of developers
According to the official time, it would be fine if we arrived at 9:30pm. Worried about being late, we arrived early before 9:00.But unexpected that we still underestimated participants’ enthusiasm, as the time we got there, the queue was already too long to see the end. No one could enter the venue without tickets registering or signing. At first, the organizers introduced the rules, actually we had already learned some , and some hadn’t been mentioned before was that you only had 3 minutes to show your product and 2 minutes for questions and answers. There were over 400 people on the scene including 70 teams, each team up to 5 persons. As soon as the Countdown started, everyone began to prepare nervously. Some teams didn't even go back to rest even if there was also a lounge nearby for a short rest.
### Determine the plan and start execution Before coming here, we had decided to use the company's developing products for the exhibition. But it is still too soon to require a full redevelopment of a system within two days. After the internal division of labor, they decided that I would write the intelligent contract. Old K was responsible for overcoming technical barriers, Old L is in charge of the project, was responsible for making plans and preparing product shows, Old C was responsible for front-end writing and back-end functionality implementation. The whole process was tense and exciting, especially at the end of the countdown, we are almost the last minute to submit the code.
### 3-minutes production show, try to impress the judges Because there were only 3 minutes, and it was required to explain in English. Fortunately, we have an old Australian programmer L. The EOS foundation had sent eight judges, each two of which was responsible for more than 10 teams, so we needed to face to two of them. During the introduction, the judges also used words like great to affirm our project. We have great confidence in the products and the judges have also given us positive comments, so we have strong confidence to enter the top 10.
### While announced the winning list, we wanted to pat thigh
At the end of the competition, we all waited for the award to be announced. They first selected the top10 to display their products, and then selected the top 3 among them. One team after another came on stage, we still waited for being mentioned, thinking that there was no hope. By the 10th team on the stage, we had already known we were out of the running! When you saw the number one project was doing a system of identity authentication, Old K wanted to pat his thigh, because we originally planned to use the product of the identification system to compete with!
### Conclusion
It must be a bit disappointing not to have won the prize, but overall, the harvest was good. Although this is a competition, there were some technical presentations, and at the meantime, there will be many mentors to give guidance. We also have a deeper understanding of EOS products during the competition. Analyzing the reason why we didn’t win, maybe the cause was that our products was a bit big for this game, on the other side, blockchain project issued token isn’t fresh, for this kind of game, we still need some new ideas to impress the judges. Make a conclusion and be prepared. Maybe the next EOS Sydney marathon belongs to us!
Congratulations @yekai! You received a personal award!
You can view your badges on your Steem Board and compare to others on the Steem Ranking
Vote for @Steemitboard as a witness to get one more award and increased upvotes!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit