The thing that I am most excited about this meetup is where it is happening, at the architecture and design museum.

The last one was at a wonderful venue as well. The organisers clearly are on top of their game.

During the five minute break between sessions I had a chance to look at a couple of exhibits, and it seemed interesting to me. Perhaps, we would be back here.

1. “How AI can bring back the original tradition of storytelling”
by Roope Rainisto

Originally, stories were told orally. Storyteller was a performer, interpreter and editor - changing things based on the listener feedback. This remained the case even in 16th/17th century.

The change started in the last five hundred years or so. Technology came and detached the story from the story-teller. The story does not change anymore. Stories are dead artifacts now, being copied and distributed across the world.

Games are a break from this fixed form. The player can influence the story.

But games are still dumb. They are on rails. Either you click through the cutscene and go to the game (shoot stuff). Or they are sandboxes where you can do a bunch of stuff but there is no story.

D&D or LARPing are examples where you have freedom and story progresses as well.

AI may bring back the intelligent story-teller. It can bring back story-telling as performance. There are a bunch of things which are possible.

The artist can be present by describing the story world not just the story. What are the ideas, the thing that you want to tell. The player needs to feel like they came to the realisation on their own.

2. “Stop Prompting. Start Commanding: How Agent Armies Build Better Systems” by Rolf Koski, Co-founder & CTO @ Elexive

The same SDLC principles should apply even now with vibe-coding. Specs must capture the requirements.

Use markdown documents to steer the AI, about your choices - stack, naming, patterns. Progressive discovery is key here - protect your context window.

There are different agent patterns -

1. Loop over itself to create a output
2. Parallel execution which results in a output

Rolf prefers Kiro and Claude Code. One alternative to Kiro is OpenSpec. I liked the idea of spec-driven development. Something to experiment with.

3. “Three Gains from Integrating Vibecoding into My Workflow”, by Christoffer Weiss, Chief Avatar Officer @ Avataria

1. Make whatever software you want to use
2. Single person team
3. Never start from zero

---

And per usual, here’s a pic from outside the venue, after the talk.