Welcome!
When you start your open source journey, there are two major milestones that you will encounter: making your first contribution and attending your first hackathon. It is a wacky event where cool ideas born out of late-night coffee-fueled coding sessions turn into awesome projects(if you prefer to drink tea or water during these sessions, that's fine too!)! π Sounds fun right? Well, before you run to register, I am going to give you some dos and donts on making it through your first hackathon.
The Do's of Hackathons
- Do pick your niche: I know, I know this sounds clich, but hear me out. Picking a hackathon is like going to Baskin and Robbins (or any famous ice cream shop in your area!) and trying all 31 flavors before choosing the flavor you actually want, so I highly recommend that you chose a hackathon that suits your interest. In my case, I decided to go with SheBuilds due to its focus on gender inclusivity and encouraging participants to be creative with their projects.
- Do pick a project that you and your teammates agree on: Just like choosing an outfit for your first date, its important for you to choose a hackathon project that screams pick me to you and your team. Itll make the late-night coding sessions bearable. For SheBuilds, my teammate, Rossella Ferrandino, and I wanted to do something for their Women Empowerment track and Dean wanted to create a chatbot. So, we combined these two ideas together and came up with Entreprenheur, a web-based chatbot that helps women find mentors and other resources to aid them in their entrepreneurial journey. Click here to view our demonstration of the chatbot. If want to use it, check out our repository.
The Don'ts of Team Hackathons
Yay, we made it through the Dos! πNow before we open the bottle of sparkling juice, here are some things to avoid when attending your first hackathon:
Dont underestimate the deadline: Im going to be honest with you, hackathons tend to be short, so there are some of your initial ideas wont a part of the final version of your project. For example, I wanted to add a feature where users can type their responses to the chatbot, but decided not to since Dean mentioned that building this feature would cause us to submit our project past the deadline.
Dont hesitate to ask for help: I know you dont want to seem like an idiot in front of your teammates, but trust me, asking for help will make the hackathon so much more bearable. For instance, I found myself struggling with finding time to write the script for our projects video demonstration, so Dean wrote some ideas, then, Rossella and I provided feedback on it. Remember, it takes a digital village to raise a hackathon project, so dont be afraid to ask.
Dont forget to have fun: Contrary to popular belief, hackathons are not always about being intense and competitive, theyre about having fun and making memories. My teammates and I would tell each other jokes, talk about how our days had been going, and share things like YouTube videos. It made the process of building our chatbot go by quickly.
Conclusion
There you have it folks! π I hope you find my tips helpful! Remember, pick a project that fits, work with your team, and have fun! Til we meet again my hackies!
Hungry for more content? Check out yesterday's post, and don't forget to click Subscribe at the top of my post and follow me on Hashnode as well as my other socials.
Credits
Black and White Art GIF by Okkult Motion Pictures
Dr. Strange GIF by Marvel Studios
Top comments (1)
Team hackathons are a whirlwind of laughter, learning, and a lot of coding, where collaboration and creativity thrive. The dos include planning ahead, setting clear goals, and ensuring effective communication among team members. Equally important are the don'ts: avoid neglecting rest, don't overcomplicate solutions, and steer clear of excessive caffeine that could lead to burnout. Like the joy a mr whippy cart brings with its delightful treats, a successful hackathon should balance hard work with fun, creating an environment where innovation and camaraderie flourish.