Last weekend I was a judge at the Toronto Startup Weekend – Library Edition and was reminded again not ony how much I love hackathons, but how unexpected they are.
The Toronto event wasn’t strictly speaking a hackathon. A hundred people met, many pitched ideas, and then people formed teams. They had to come up with a business idea and pitch it to five judges, explaining their idea, perhaps including a demo, showing their research (including user surveys if appropriate), and making the case for it as a sustainable business enterprise. (Non-profits welcome.) It was a fantastic event.
But to keep things simple, consider a classic hackathon: developers get together for a day or a weekend and are challenged to write working code, usually constrained to a particular genre (e.g., games) or using an open data set (e.g., the DPLA hackathon or the Open Syllabus Project hackathon). And the amazing thing is that they do it.
Just think about all that had to happen to make a hackathon possible and not a cruel joke.
We need browsers and HTTP and the ability to request data through them.
We need well-documented, standard ways of requesting that data.
We need open sources of data.
We need Open Source software to let us build on work done by others.
We need frameworks that let us do easy things incredibly easily.
We need libraries so we can do complex things incredibly easily, such as visualizing data.
We need an Internet to connect programs to data, software to users, and everyone to everyone.
We need an ethos that encourages sharing, experimenting, and prototyping — finding what’s right in a project not all that’s gone wrong or has been left unfinished.
I love hackathons.