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
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API