=Paper=
{{Paper
|id=Vol-3077/keynote2
|storemode=property
|title=Effective participation in programming contests
|pdfUrl=https://ceur-ws.org/Vol-3077/keynote2.pdf
|volume=Vol-3077
|authors=Bohdan V. Hrebeniuk
}}
==Effective participation in programming contests==
<pdf width="1500px">https://ceur-ws.org/Vol-3077/keynote2.pdf</pdf>
<pre>
Effective participation in programming contests
Bohdan V. Hrebeniuk
Zaraffasoft, 2 Mystetska Str., Kryvyi Rih, 50006, Ukraine


                                      Abstract
                                      Hackathons are one of the most popular ways to organize competitions between programmers. Usually,
                                      during a hackathon, teams are offered a task, for the solution of which a certain time is allocated, for
                                      example, a day. As a solution, the team must develop an application. The jury evaluates its functionality,
                                      originality, creativity of the approach to the solution.
                                          Hackaton is an ideal place to test your programming strength; solid platform for launching and
                                      testing startups; effective way to get job offer; also good place to have fun.
                                          The experience of multiple participation in various competitions allowed us to summarize the main
                                      conditions for successful participation.
                                          The first such condition is the correct formation of the team. The team should have specialists in
                                      various fields who are ready to take on different roles, for example, front-end or back-end. At the same
                                      time, the amount of work between different developer roles is not uniform. For example, working on
                                      a frontend application requires more time and effort throughout the entire task process. Therefore, it
                                      would be advisable to strengthen the team with an additional front-end developer or full-stack developer
                                      who can change his role in the course of solving the problem. It is desirable that one of the frontend
                                      developers is a good designer. It is also advisable to include in the team a specialist in the application
                                      area for which the application is being developed.
                                          The second condition is a thorough preliminary technical preparation: creating generic solutions;
                                      creating repositories; server rental; preparing presentation.
                                          The third condition: rational distribution of time. It is advisable to make the generation and selection
                                      of ideas as the first stage of development. Brainstorming is a good way to do this. You can allocate 1-2
                                      hours for it. Then stop at the best idea and focus on its implementation.
                                          An important intermediate stage should be the selection and systematization of all the functionality
                                      of the future program.
                                          In the process of developing a program, it is important to run side quests from time to time. For
                                      example, it might be a short questionnaire describing a project and asking you to rate it. The questionnaire
                                      form can be sent to friends, acquaintances, and get feedback from them. The presentation of these
                                      statistics will help not only improve the program, but also get additional points from the jury.
                                          It should also be remembered that participation in hackathons is associated with strong emotional
                                      stress. An important condition is constant communication between team members, voicing problems
                                      that have arisen, etc. You should also remember to rest, especially before the final stage - the presentation
                                      of the solution.
                                          Much depends on the quality of the presentation, its completeness, brevity and, of course, positive
                                      tone.
                                          And remember that the end of the event does not mean the end of the work. It is imperative to analyze
                                      the work done, to note the positive and negative points in order to take into account the experience
                                      gained in further work and new competitions.



CS&SE@SW 2021: 4th Workshop for Young Scientists in Computer Science & Software Engineering, December 18, 2021,
Kryvyi Rih, Ukraine
" bogdan020699@gmail.com (B. V. Hrebeniuk)
~ https://www.linkedin.com/in/bohdan-hrebeniuk-006ab7221 (B. V. Hrebeniuk)
 0000-0002-0423-8476 (B. V. Hrebeniuk)
                                    © 2022 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
 CEUR
 Workshop
 Proceedings
               http://ceur-ws.org
               ISSN 1613-0073
                                    CEUR Workshop Proceedings (CEUR-WS.org)



                                                                                                        2

</pre>