Posted on 03-21-2012
I’ve spent a lot of time trying to track on what gets created at hackathons. Some innovative programming occurs at these events and I’d say 98% of it is forgotten by Monday morning.
I think a lot of attention is given to the myth that hackathons are about building startups. When in reality, how many startups come out of hackathons? In my opinion the top three things that come out of a hackathon are:
- Marketing - For the event organizer, sponsors and for participants.
- Talent Acquisition - There is some seriously talented folks attending hackathons.
- Networking - Hackathons are a great place to meet people, network, make friends and sure maybe a co-founder.
Beyond that I think there is a lot of code that gets generated at hackathons, that really never goes anywhere. Much of this code is not immediately VC fundable, but still some of it is really good. And I see a lot of kids spending whole weekends writing the same or similar code as I saw the weekend before.
To help remedy this, I suggest that event organizers use Github. Just like every hackathon organizer should identify a Twitter #hashtag for the event, you should setup a Github organization and add your hackers as users. Encourage them to commit their code through-out the hackathon, and wrap up the weekend with a nice README file of their project.
Seems like a great way to showcase what was built over the weekend, make the intellectual property open and accessible for other people to use, and make it easier for other hackathon participants to build off what has already been created in the past.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems