What tattoos and software projects have in common

In this session, we’ll explore why getting a tattoo and building software aren’t as different as they might seem. Both require vision, trust, and a steady hand—whether it’s ink hitting skin or code hitting production. We’ll look at how great artists and great developers share a respect for careful planning, a willingness to iterate, and the courage to commit. By the end, you’ll see that whether you’re holding a tattoo gun or a keyboard, the path to something remarkable is forged through patience, care, and embracing the unexpected. As a tattooed software guy i know of what i am speaking :)

5 common mistakes in DevOps strategies

Devops is one of the buzzwords of the recent years and thus many companies felt the urge to jump the hype train and implement what they considered to be Devops. In this talk i highlight 5 of the most common issues i met during my career when companies implemented their Devops strategy and explain why i consider them issues, and propose potential solutions.

Avoid the Ivory Tower of Software Architecture

In this talk I will tell you a story about an architect and a dev team wanting to develop a perfect product...the outcome is...well see and hear for yourself :)... In the talk I will point out common problems in the communication betweeen developers and architects, and show potential mitigations.

The art of quitting

Quitting. For most people this has a sound of failure and negativity, but in my talk i want to show why quitting is much more than this. In fact it is an essential tool for any founder, manager, engineer or poker player. I will show what makes quitting so hard and how we can mitigate the factors that let us quit too early or too late. Furthermore i will demonstrate how we can optimize our decisions if and/or when to quit at the right time. Quitting is an art. So let's practise it.

Keep It Simple: Maybe You Don’t Need Microservices or Kubernetes… Yet

In a world buzzing with talk of microservices and Kubernetes, it’s easy to assume your project needs all the latest bells and whistles right from the start. But sometimes, you simply don’t—at least not yet. In this session, we’ll apply the “You Ain’t Gonna Need It” (YAGNI) principle to cut through the hype and focus on what your project really requires today. Instead of plunging into complex architectures prematurely, we’ll explore how an evolutionary approach can guide you toward simpler solutions that grow and adapt as your needs mature. Join me for a candid conversation about sidestepping unnecessary complexity, recognizing when (and if) the fancy stuff truly adds value, and setting the stage for long-term success—without overengineering from day one.

The Dark Side of MACH

MACH (Microservices-based, API-first, Cloud-native, and Headless) architectures are taking the e-commerce world by storm, promising a future of flexible, scalable, and fast-moving systems. But before you jump on board, it’s important to take a closer look at what you might be getting into. In this session, we’ll explore the often overlooked “dark side” of MACH—those hidden challenges that can catch you off guard if your team is coming from a traditional, monolithic background.

Rather than painting MACH as all sunshine and rainbows, we’ll talk openly about the tricky parts: juggling multiple microservices, handling complex data flows, and managing an evolving ecosystem of tools, platforms, and vendors. Drawing on guidance from the MACH Alliance (machalliance.org) and insights inspired by resources like Building Microservices by Sam Newman (O’Reilly, 2015) and Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution, 2019), we’ll discuss how to spot the real needs of your current system, decide if MACH is right for you, and adopt best practices that keep complexity in check.

Join me for a frank, practical conversation about what it really takes to shift from monoliths to MACH. You’ll walk away with a clearer sense of how to manage the complexity, upskill your team, and shape a roadmap that builds on what’s essential—without getting lost in the hype.

a talk for people (within or outside the ecommerce domain) to get a reality check about MACH architectures beyond the hype. After this talk they should be able to understand if MACH is for them or not and get a little cookbook for the biggest challenges.

Why Your CEO should care about DORA Metrics

When we talk about DORA metrics—those key signals like lead time, deployment frequency, and time to restore—we’re often speaking in a language that seems designed for engineers. But here’s the twist: these metrics aren’t just technical trivia. They’re a powerful window into how healthy and adaptable your entire organization really is. In this session, we’ll unpack the DORA metrics and show why even your CEO should care about them—because behind every number is a story of market agility, team effectiveness, and long-term resilience. Drawing on insights backed by DORA’s research and the widely referenced “Accelerate” book, i try to translate engineering shorthand into executive-level understanding. By the end, you’ll walk away with a clear sense of how these metrics connect directly to strategic goals, making them indispensable tools for guiding enterprise-wide decisions. It’s time to bridge the gap between the engine room and the boardroom.

this talk is not just for DevOps engineers or sofware people. also executives and C level managers gain an important insight about how these metrics can make or break their business goals.