Your first hackathon: prepare well and get your project to a working demo
Go into your first hackathon with a task you can finish and explain. For a beginner, a good result is concrete: your team builds a working user flow, submits the required materials on time and understands what to improve. The judges decide who wins. The scope of your project, access to your files and readiness to demonstrate it depend largely on you. A hackathon is usually a time-limited event…
When attending your first hackathon, it's crucial to approach the event with a clear goal in mind. A realistic objective could involve creating a fully functioning user flow for your team's project. Ensure the project is completed on time and all necessary materials are submitted in a timely manner. The judges will be evaluating the quality of your work, so make sure your team is prepared to demonstrate the project effectively.
The scope of your project, access to your files, and readiness to showcase it will largely depend on your own efforts. Hackathons are time-constrained events where participants create solutions and present them. Some events require functional code, while others accept research, hardware prototypes, or mockups. To prepare for the event, start by thoroughly reading and understanding the participation rules outlined on the event page.
Pay close attention to requirements related to age, team composition, location, and in-person attendance. Note the start time, submission deadline (including time zone), and presentation format. Be sure to document exactly what needs to be submitted, as different requirements may call for a repository link, deployed application, slides, or a video.
If a video is required, test your microphone and recording setup beforehand. In case your project involves hardware, inquire about bringing your own equipment and the availability of power supply. Obtain specific answers to your inquiries from the organizer, as verbal agreements with volunteers may not be recorded. Before starting the project, ensure you have all the necessary tools installed and functioning properly.
Test your editor, repository, and hosting service, and conduct a test screen recording to check audio quality. Practicing by working on a small learning project can help you familiarize yourself with the tools, but remember that the code you develop for this purpose might not be usable in the hackathon, depending on the rules. Don't forget to bring a charger and any required adapters.
For in-person events, find out about rest areas, dining options, venue accessibility, and closing times. Avoid relying on unfamiliar laptops, shared accounts, or temporary access to paid services as the basis of your project. Be honest about your skills and abilities. For example, stating "I can build two screens and connect a form to an existing API" is more constructive than "I'll handle the entire frontend."
Clearly communicate what you have independently accomplished, what you've learned through tutorials, and what skills you hope to acquire during the hackathon. This information will help you determine a suitable project scope that doesn't rely on discovering missing skills at the last minute. Explain the extent of your independent work, your reliance on tutorials, and areas you wish to learn during the event. This will assist you in setting realistic goals for your hackathon participation.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
