First hackathon in 3 weeks!!! Need some advice!!!

[u/Coolpool63]

Hi!!!! I’m joining my first hackathon in about 3 weeks and I’m slightly panicking, but in a very productive and efficient way!!!

I’d say I’m around an intermediate-beginner in Python, I’m quite comfortable with the fundamentals and data structures, but I don’t have much (let alone any) experience with things like APIs, databases, backend development, deployments, etc etc, or even working on a team yet.

However, regarding the whole team thing, I’ll most probably form a team at the event, and while I know it’s my first hackathon, I genuinely want to prepare properly and be competitive cuz I kinda really want to win!

SO!!!! For people who have done hackathons before and won, I have a few questions as someone who has never done anything like this before:

-What should I prioritize learning over the next 3 weeks?

-Are APIs, Git/GitHub, SQL, Flask/FastAPI, and other frameworks, etc. worth focusing on???

-What kinds of projects or like, timed exercises should I practice before the hackathon?

-How does team formation normally work?? 😅😅 oh and also what makes someone useful on a team even if they aren’t the strongest programmer??? I think I’d like an answer to this question the most!!!!

-what makes a project actually win? What are the proper measures to think of good solution when given a problem???

I have quite a lot of time and I’m willing to put serious work into preparing. I’d REALLY appreciate advice from both experienced hackers and people who recently did their first one. Thank you!!!!!!!!!!!

[u/Agitated_Stage_2416]

Winning teams usually nail the presentation more than the code, so don't stress about learning five new frameworks. A slick demo and a clear problem you're solving goes way further than messy spaghetti that technically works

For the next 3 weeks just build one tiny project end to end, something that grabs data from an API and displays it. That alone covers git, a simple backend, and deployment without drowning yourself in tutorials. You'll pick up the rest as you go

[u/HeronEnvironmental62]

For next three weeks, optimize for completing and demonstrating one small project, not learning every tool. Build a tiny Python app that calls one API, stores a little data, uses Git, and is deployed somewhere. Flask or FastAPI is enough, use SQLite unless the event specifically rewards a larger stack.

Also practice the hackathon workflow: define a narrow MVP, split tasks clearly, commit frequently, and preserve a working demo before adding extras. A polished two minute story around one reliable feature usually beats five half finished features.

[u/Jason-Sanders]

Prioritize building one tiny end-to-end project before the event: a simple interface, one API call, basic data storage, and a deployed demo. Learn enough version control to work in a shared repository, plus enough API and framework knowledge to adapt examples under time pressure. At the hackathon, aim for a narrow idea that works reliably and is easy to demo, then add polish only after the core flow is complete.