How We Ran a Pirate Themed Hackathon at Mimiquate

Culture

Our previous hackathon followed the classic formula. Each team came up with an idea, built it, and presented it. There was no specific learning goal, and the winner was simply the idea the jury liked best based on a set of criteria. It was a good time, but we kept asking ourselves: what if a hackathon could be more than that?

Kevin Expósito avatar

Kevin Expósito

7-9 minutes - November 24, 2026


This time we wanted something different. The main goal was for people to get hands-on with new tools and learn Spec Driven Development. We also wanted the event to be more dynamic than the typical hackathon, with more surprises and more interaction between teams.

From Mario Kart Power-Ups to Pirates

Our first idea was to bring in "powers", something like Mario Kart. Imagine teams getting power-ups and using them to help themselves or slow down their rivals mid-race.

Then we pushed the idea further: what if teams could steal each other's ideas? We knew right away it could turn into chaos. But chaos, in the right dose, is also what makes things memorable.

We needed a theme that could hold all of this together, one where stealing, sabotage and unpredictability felt natural. That's how we landed on pirates.

FOTO DEL DIPLOMA

Life On The High Seas

With the pirate theme, the rules practically wrote themselves:

  • Crew kidnapping: teams could capture members of other crews.
  • Pirate dares: challenges like programming with a hook, or being adrift for 5 minutes without internet.
  • Public visibility: everything that happened was visible to everyone, so there was always something going on to follow.
  • Every sabotage and every plot twist became part of the story of the event.

    FOTO DEL CARTAS

    The App That Ran the Seas

    To make all of this work, we built an app that acted as the heart of the hackathon. It announced events in Slack as they happened, and it had a main page where everyone could see which teams were currently affected by a dare or an attack, and which ones were sailing free.

    FOTO DE LA WEB

    What the Crew Told Us

    After the event, we sent out a survey to get real feedback. The results were very positive. People felt they had learned what we were aiming for, and the response around the learning part was strong. Just as importantly, people said they enjoyed the experience. The dynamic made them step out of the ordinary, and that was exactly what we wanted.

    The Storms We Hit

    Not everything was smooth sailing. Here's what we learned the hard way:

  • Time management is critical. A format with this many moving parts needs a very careful schedule, and it's easy to underestimate how much time the dynamics take on top of the actual building.
  • The cards created a lot of edge cases. When can a card be used? How exactly? How do you hand them out fairly so no team gets an unfair advantage? These were questions we spent a lot of time on before the hackathon, and we had a rule for almost everything.
  • Then the day arrived. Things moved fast, and many of those carefully designed rules got lost along the way. In the end, fun took priority over strict rule-following. Looking back, we think that was the right call, but it's a good reminder that no plan survives contact with a room full of excited pirates.
  • What We Take Away

    A hackathon doesn't have to be only about who has the best idea. When you design the format around a clear learning goal and add a layer of playfulness, you get both: people who learn something real, and a day they'll actually remember.

    We're already thinking about what's next. We'll almost certainly run another hackathon next year, and with everything we learned.



    paper airplane

    Thoughts? Like what you just read?

    Let's keep the conversation going. Share it on social or reach out and tell us your take.

    mimiquate petmimiquate pet