- On average, hackathons are one of the best opportunities to learn real skills, produce resume projects, and network with peers and employers.
- Anecdotally, we know that many/most people join Developer DAO for the same reasons.
- We should invest in processes and tools that help members enter hackathons and have successful experiences within them.
I’d love to see a DAO team take ownership of hackathon team prep. I asked this question on the bird app and got some great feedback.
- Templates/starter kits optimized for hackathons would be a great public good produced and maintained by DAO members. Similar things exist, but I believe it would be great for an internal team to own those decisions and dogfood tools that we create.
- Hackathons are typically tight timelines. Providing great documentation/content/workshops using those templates would help people get moving quickly.
- Design plays a large role in hackathon evaluations; all you get is a first impression. Templates should include attractive component libraries, etc.
- Re: first impression importance, template slide decks could be offered by the DAO to aid in professional presentations of projects.
- Match-making for projects is a big problem space with a lot of opportunity for experimentation.
- Teams need to have some bases covered: front-end, back-end/smart contracts, design, etc.
- Ideally, teams are aligned on project interests, e.g., defi, NFTs, network, causes like environmentalism, etc.
- Opportunity to grow network in specific direction, e.g., for web3con, @camiinthisthang offered specific opportunities for women to meet and form teams.
- A little randomness can be fun.
If you’re interested in joining or leading a team to bring some of these ideas to life, please speak up!