When to do a hackathon?

A hackathon format becomes interesting when you are facing these situations:

  1. When in the middle of a (stagnant) problem; when you are talking in circles.

  2. When you want to bring practicality to the table, or new and tangible focus to the debate.

  3. When the solution is dependent on collaboration of others and there are many stakeholders involved.

  4. When there are insecurities or mistrust regarding the possibilities of technology.


Why a hackathon?

Building is not the same as talking. Talk brings abstraction and complexity. By building something in an app or website interface, you materialize your ideas. Do rather than talk. We <3 pragmatism.

Switch up a 6 person meeting to a 6 person hacking. In a hackathon CEOs collide with data scientists. Researchers with creative designers. Government officials with back-end developers. All in one table for +30 coding hours (while having snacks, coffee and yes beers:). This is a recipe for a jumpstart! It can catapult your collaborative solution to the next level.

A hackathon is a neutral space for diverse groups of people to join in. They collaborate as peers committed to solve one problem. This is a natural setting for people to trust each other. Particularly useful for farmers who are sometimes wary of the vendor dominated software/technology environments.


A hackathon is:

A hackathon is a process for rapid prototyping and development of data-driven solutions; a highly energetic and effective pressure cooker. Hackathons are a means to encourage collaboration, knowledge exchange and cooperation to help find innovative uses of data.

This event typically lasts several days (32-48hrs) and a large number of people meet to engage in collaborative computer programming.

With FarmHack.NL we have taken this format to the farm. It's not just about people who understand data, code and technology - it gets exciting when you bring them together with farmers and people with domain knowledge. We bring these parties together.