You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.
At my first hackathon, I didn't know how hackathons worked or how to finish a project in a few days, and my group and I ended up rushing our code and not being satisfied with it.
We should create a section in our app called "A Hackathon Project Timeline Tips" or something similar that will give people, especially first-timers, an idea of how hackathons work and what they should have done by when, in order to stay on track. For example: 1-2 hours finding a group and brainstorming, then 20 mins to divide up roles, etc.
The text was updated successfully, but these errors were encountered:
At my first hackathon, I didn't know how hackathons worked or how to finish a project in a few days, and my group and I ended up rushing our code and not being satisfied with it.
We should create a section in our app called "A Hackathon Project Timeline Tips" or something similar that will give people, especially first-timers, an idea of how hackathons work and what they should have done by when, in order to stay on track. For example: 1-2 hours finding a group and brainstorming, then 20 mins to divide up roles, etc.
The text was updated successfully, but these errors were encountered: