Posted on 11-13-2012
Hackathons are a fertile environment for generating code based upon the ideas of its attendees. However, much of the innovative programming that occurs at these events is forgotten the day after the event ends. This process tends to leave developers working on the same ideas over and over, without much continuity.
To help remedy this, hackathon organizers can use Github to store code that is generated by all attendees. Organizers can encourage all developers to commit their code through-out the hackathon, and wrap up the event with a README file of their project as part of the presentation process.
Github can be 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.
Using Github for a hackathon can generate extra marketing for the event as well as the hackathon organizers.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections