What is the reason to experiment in the conference space?

Back to Routine

After the conference has ended, it is very common to get back to the office, fire the code editor, try some new stuff and… just forget about it after a week.

No Collaboration

We usually collaborate only with our co-workers and rarely, with people we don’t know personally over an Open Source project, but still, most of the time is just us and the code.

No Learning Process

Learning is a complicated process, we go through many steps while learning something. The current conference model makes learning hard, listening to somebody on a stage

No Socialization

Socializing is an important part of a conference, for some people is the main reason to go to a conference, but the chances to socialize are limited to breaks and after-party.

We want a new...


The format has been developed by many people, collaborating in a single document, trying to get the best of other formats like hackathons and un-conferences.


The introduction is going to be a 5–7 minutes presentation from the mentors about a topic to run experiments, every attendee can then understand what the group is about and later join it for experiments.


Every mentor is going to have a group of people, experimenting on the topic they prepared, maybe with a final goal in mind, but they might also be totally open. All the attendees are going to work with other people they probably never worked with, exchanging knowledge while normalizing the struggle. We’ll shake things up regularly and have 3–4 sessions with each others.


Hacking is important, broadcasting knowledge even more. One mentor is going to be dedicated to help attendees interested in presenting what they have done during the day to all the other attendees in a fire-talk, a 5 minutes technical presentation about a topic, which are going to take place at the end of day.

Read more on Medium.