A way for one program to talk to another. When people say "use the weather API", they mean their code asks another service for weather data instead of calculating it.
The part of an application you cannot see — the server, the database, the logic. Contrast with frontend.
A parallel copy of your code in Git where you can work without disturbing the main version. Merged back in when it works.
Something not working as intended. Not a sign of incompetence — professional software is mostly the process of finding and fixing these.
A mid-event progress update some hackathons ask for. Usually not scored; it exists so organisers can spot teams that are silently stuck.
Downloading a copy of a code repository to your machine.
One saved snapshot of your project in Git, with a short message describing what changed.
Showing your project working. At most hackathons this means a recorded video rather than a live presentation.
Putting your project somewhere on the internet so other people can open it, rather than it only running on your laptop.
A pre-built structure that handles common work so you do not start from nothing. React, Django and Flask are frameworks.
The part users see and interact with — the pages, buttons, layout.
The tool that tracks versions of your code. Not the same thing as GitHub.
A website that stores Git repositories online so teams can share code. GitLab and Bitbucket do the same job.
In this context, something built quickly and roughly to prove an idea. Nothing to do with breaking into systems.
The phase at the start where you decide what to build. Should take under an hour; frequently takes six.
The published criteria and weightings judges score against. Read it before you build, not after.
The opening session where rules and themes are announced and the clock starts.
Someone available during the event to unblock you. Asking them early is the single highest-value thing a first-timer can do.
When you and a teammate changed the same lines and Git needs you to decide which version is correct. Routine, not a disaster.
Minimum Viable Product — the smallest version of your idea that still demonstrates it. This is what you should aim to finish first.
Code published publicly for anyone to use, usually under a licence. Using open-source libraries at a hackathon is normal and allowed.
Explaining your project persuasively and briefly. Usually part of the demo video.
A proposal on GitHub to merge one branch into another, so teammates can review before it lands.
Sending your local commits up to GitHub so others can see them.
The main documentation file in a repository. What it is, who it is for, how to run it. Judges read this.
A project folder tracked by Git, usually hosted on GitHub.
How much you are trying to build. "Scoping down" means cutting features to finish on time, and it is the most useful skill at a hackathon.
The combination of technologies you are using — for example "React and Firebase".
The final package you hand in: repository link, demo video, and write-up.
A category within a hackathon. Some are by theme, some by experience level — first-years often have their own.
A rough sketch of what a screen will look like, made before building it. Ten minutes on paper saves hours of rework.
If you hit a word during the event that is not here, tell us and we will add it.
Suggest a term Read the guides