Eight Choices. One Team. One Long Night. Our first hackathon: learning, problem-solving, and building together

At 4 p.m., our hackathon adventure began in the auditorium, buzzing with excitement and hunger. As first-timers, we were eager to dive in. However, before the coding commenced, we attended two hours of panel discussions, gathering an abundance of ideas and knowledge beyond our expectations. A crucial takeaway was to always question "why" when interacting with AI.

Focusing on "how" before we understood the problem could lead to endless loops. This insight proved useful as we faced our first major challenge: selecting which problem to solve. We entered with the right mindset – learning, gaining experience, and understanding open source. Our goal wasn't winning, but personal growth, teamwork, and leaving with more knowledge than when we arrived.

After the sessions, we grabbed snacks and began strategizing. Our three-member team divided tasks evenly across UI/UX, backend, coding, and research, combining various strengths and learning from one another. Then came the difficult part: eight problem statements to choose from. We examined each option, considering our skills, interests, the time available, and the feasibility of building something worthwhile together.

Opinions differed, but every perspective was valued, enriching our conversation, albeit extending the decision process beyond our initial expectations. Once we selected the eighth problem statement, uncertainty eased, and we could picture our potential project. This small victory felt like a significant turning point, giving us direction and confidence.

As we commenced building, unforeseen challenges emerged. Whenever we encountered roadblocks, we discussed them and tried alternative approaches. Often, a new idea sparked more discussion, reshaping our solutions. Every opinion mattered, as each contributed a unique possibility. We maintained a collaborative atmosphere, working together on UI/UX, backend, and research, rather than isolating ourselves.

Around 11 p.m., the room radiated focus and energy. Post-dinner and midnight snacks, our determination kept us going. By then, we had gained insights on how hackathons demand discipline, thoughtful task division, active listening, and continuous learning when progress stalls. By 5:30 a.m., with a full night's work behind us, we had nearly completed our project.

Our code was on GitHub, the pitch deck prepared, and we polished the final touches. The remaining task was practicing our pitch, and we were ready to present. Tired, yet proud and hopeful, we looked forward to sharing our work and receiving feedback. No matter the outcome, we knew we'd given it our best and were excited to present our achievements.