Talk 1: How I automated my life with MCP Servers - Cedric Clyburn & Legare Kerrison
Being a developer these days means you’re not only writing code, but also a Linux admin, a DevOps engineer, you name it! Thankfully, the Model Context Protocol (MCP) has made it significantly easier for me to ask my natural language questions, such as “What’s consuming the most memory in our dev cluster right now?”, and quickly receive a response. Hint: It was Prometheus!

What you’ll learn in this session is a straightforward way to build your own local “AI Agent” using open source technologies to interact with various API’s and tools. We’ll take a look at the most common MCP Servers that developers are using today, think Git, Databases, Dev Tools, and more. Plus, we’ll have some fun, and chain multiple tools together to automate your daily standup!

Talk 2: The fundamentals of Agentic Coding (AKA Vibe Coding) - Theodor René Carlsen
AI, whether we like it or not, has fundamentally changed the ways we work with code. In the beginning, many swapped out Stack Overflow for ChatGPT, moved from editing code to autocompleting with tools like Copilot, but now we are seeing more tools that that can write large parts of the solution for you.

Most people will relate to the feeling that “vibe coding” or “agentic coding” is a moving target, where both the models and the tools evolve at near-exponential speed. In this talk, I aim to reduce the sense of FOMO many might get when they hear people using these tools to write and refactor large parts of their codebase for them. Whether that FOMO comes from LinkedIn, X or your boss thats fully convinced that vibe coding is the future, we will try to stay grounded when meeting this new technology.

We will cover the basics so that you can actually understand what these tools are about: what they can and what they cannot do, what is mostly hype and what is actually worth checking out. And yes, we will also try to define the term "agentic coding" .

Talk 3: The Design Systems Graveyard - Kristoffer Nordström
It is said you can't succeed in building a Design System without having done so before. But building a Design System is easy - maintaining and making it grow is much more difficult. During the years many Design Systems have failed and ended up on the Design Systems Graveyard. I will share some trips and tricks that will make it less likely that you fail in your attempt of succeeding with one. Join me on a story about planning, categorising and sorting and about handling human beings and collaboration. This also have something in common with The Gentle Art of Swedish Death Cleaning. If you fail maybe your Design System will end up on The Design Systems Graveyard.