Hackathons are community events, and beginners show up at all of them. Organizers expect first-timers, teams take them, and nobody checks your resume at the door. Most first-timers who struggle didn't lack skill; they showed up with no plan for the weekend. This page is that plan: one table that covers the whole arc from signup to the week after, a packing list, and four opinions we'll label as opinions. It stays generic on purpose. Pick your event from an organizer's page or a listing you trust; nothing here promises you a spot at any of them.
Before, during, after — the whole weekend in one table
Stage
Focus
Generic tips
Before
Decisions you don't want to make tired
Pick your team early. Roles agreed before kickoff beat roles negotiated at midnight.
Confirm dates, rules, and the submission deadline on the event's own page, in its timezone.
Choose an idea small enough to demo. Write the one-sentence version down.
During
A working path, not a big idea
Ship small. One end-to-end flow that runs beats three features that don't.
Check in with your team on a schedule. Quiet drift is how teams lose the last day.
Record the demo while it works. Note every deadline change the organizers announce.
After
Keep what you learned
Write a retro while the weekend is fresh: what went well, what ate time, what you'd cut.
Publish or clean up the repo so future-you can find it.
Stay in the community channels. Most people find their next team there, not on a jobs board.
Print this page (Ctrl+P / Cmd+P) and keep the table next to your laptop for the weekend.
Packing checklist — 5 items in the bag
Laptop + charger. The charger is the item people forget, and the item everyone ends up borrowing.
Every cable and adapter your setup needs. Monitor dongle, spare USB cable, whatever your demo machine requires to present.
Water bottle and snacks. Venue food runs out at exactly the wrong hour. A stash buys you decision-making time.
Headphones. For focus blocks, for calls with a teammate, for the loud hours after midnight.
ID, wallet, and the registration confirmation. Some venues check both at the door. Screenshot the confirmation in case the wifi is down.
4 opinions for your first one
These are opinions, not rules. Disagree freely.
Sleep beats the all-nighter. (Opinion.) Tired teams make scope mistakes at 2 a.m. and then spend day two debugging them. A rested team demos better than a heroic one.
Ask for help in the first hour. (Opinion.) Mentors and community channels exist at these events for exactly this. The beginners who ask early finish; the ones who sit stuck quietly lose a day.
Plan the demo before the code. (Opinion.) Once you know the 30 seconds you'll show, you know exactly what to build. The reverse order is how projects grow three heads.
Leave the last day lighter than you think. (Opinion.) Buffer time for recording, rehearsing, and the submission form is what separates projects that land from projects that explain themselves in a README.
Where the verification habit comes from
Our companion product is a 2026 web3 events & hackathons calendar, and its README states the sourcing rules worth copying before you commit to any event, anywhere. Quoted verbatim:
"Curated calendar of 45 web3 hackathons, conferences and popup cities from September 2026 through Q1 2027, plus 2 bonus entries for mid-2027."
"No dates or prize pools were invented. Entries where only an approximate deadline could be confirmed are marked with ~ in the dates field." … "Hackathon deadlines shift; always confirm on the registration URL before committing."
This page borrows that discipline, not the data. It names no events and tells you nothing about where to compete; the organizer's own registration page always outranks any calendar, including ours.
Page facts
Item
Value
Stages covered
Before / during / after, 3 generic tips each
Packing checklist
5 items
Opinions
4, each labeled as an opinion
Format
Free HTML page, printable, no signup
Event claims on this page
None. Pick events from organizer pages or listings you trust