Hackthon checklist
NOTE This is my living checklist on hackathons
For organisers
- Keep messaging consistent
Especially around timing. Be clear on any overheads and potential delays (e.g. sign-in, identity check, chaperone/escort) - Compile and share relevant resources ahead of time
This is especially relevant if there is scope to work with large datasets. - Limit non-productive time
Or, better said, balance background and context giving with time for doing. - Consider a separate preparatory session
If the focus of the event is highly specialised, consider holding a prep session in-person or online ahead of the event. - Ensure facilitators are always there
If you provide facilitators, ensure they are reachable and engaged. It is also important to keep an eye on folks that are less engaged, and help - Provide a steady supply of coffee
Having structured breaks is great, however a steady supply of warm/cold beverages goes a long way to fuel the participants without distracting from the task at hand
For participants
- Prepare ahead of time
Download any large datasets, check additional tooling and resources shared by organisers. - When joining as group, align and test your development environments and tooling This will ensure you don’t suprises during the event, and can work together effectively.
- Bring extra paraphernalia, but not too much
Bring your charger, cables, adapters (e.g. HDMI), a flash drive in case you need to move data quickly - Set a deadline for deciding
Oftentimes there will be multiple ideas and avenues to pursue. It is better to try 2-3 of them, than take all the time to settle on one thing. - Make space for smaller teams if needed
IMHO, a good size is 4-5 people. - Designate a leader, and listen to them
If everyone leads, no one is. - Leave time to present
Sharing and presenting off-the-cuff doesn’t come easy for most people. - Don’t forget to have fun!
It is easy to get lost in the task or become too competitive. Make sure you’re enjoying the process, and others do too.