What Hackathons Actually Taught Me

Source: Dev.to

There’s a specific kind of panic that hits when your app is broken, your teammate is silent, and the deadline is near. Nobody warns you about that part.

At my first hackathon, I joined with zero experience, zero certainty, and one thought: Bro, I’m just going to raw‑dog this rather than do nothing and regret not joining.
No strategy. No confidence. Just the quiet fear of regret being louder than the fear of embarrassment. Somehow, that was enough to get me in the door.

What happened after changed how I build things.
Three hackathons. Three hard lessons.

NASA Space Apps Challenge — Learning to Communicate

Our team built SierraVision – a web app that visualizes environmental changes in the Sierra Madre mountain range over time, helping people understand what’s at risk if we lose one of the Philippines’ most critical natural barriers.

• The idea was good. The execution was a mess.
• We were all beginners. Nobody took the lead. Nobody communicated clearly.
• Ideas stayed in our heads and never made it into the project.

By the deadline we were rushing and submitting whatever we had. The project wasn’t polished, but we learned that an idea poorly communicated is an idea poorly executed.

Build and Ship 24‑Hour Hackathon — Learning to Work with Strangers

I showed up alone on purpose. My weakness was working with people I didn’t know, so I walked into a 24‑hour hackathon without a team, found a stranger, and built Sola‑AI – an AI‑driven health assistant that gives personalized wellness recommendations and helps clinicians with structured treatment plans.

• We finished and presented. The judges complimented our design, but we didn’t place, and it stung.
• Despite a sub‑optimal workflow and a shaky pitch, we shipped something real in 24 hours with someone we met that same day.

Shipping something imperfect beats protecting a perfect idea in your head.

Agora Voice AI Hackathon Manila 2026 — Learning to Perform Under Pressure

I brought my thesis groupmates to test how we’d work as a team under pressure. We built ALON – a child‑centered speech‑practice app where kids aged 5–13 train their pronunciation with an AI speech coach in real time, powered by Agora’s Conversational AI, Groq LLM, and Microsoft Azure TTS.

• We had around 9–10 hours total—including brainstorming – and it never felt like enough.
• Every decision was rushed; every feature was a trade‑off. We constantly chose what to leave behind, but we kept moving.
• We finished and submitted on time, then were called for the Top 10.

We weren’t ready for the stage, felt nervous, and our presentation wasn’t as clean as we wanted. Still, we showed up, held our ground, and ended up in third place. That moment sparked a sharper feeling than disappointment: frustration.

Seeing how close we came flipped a switch. The competitiveness didn’t fade; it got louder. Each hackathon handed me the same truth in a different form:

There will always be room to improve.
The gap between where you are and where you could be isn’t something to fear; it’s why the effort is worth it. Imperfections aren’t the problem—they’re the invitation to come back better.

Takeaways

If I could go back to before my first hackathon, I’d say three things:

1. Just show up. Fear fades, but the question “what if?” doesn’t.
2. Talk more. Communication isn’t a soft skill—it’s the highest‑priority feature.
3. Finish the job. Shipping something imperfect beats protecting a perfect idea in your head.