The archive
Forty-two talks since 2016. Twenty-nine I could still track down — each one started as something that was bugging me at work. Video and slides are linked where they exist; the other thirteen lost their recordings, slides, or both, so they are not on this page.
2024 · Talk
Statista built ResearchAI to turn long lists of search results into short, well-sourced answers. The talk walks through that journey: retrieval-augmented generation over their own data, the cost and latency of each request, how hard it is to staff a team for a technology this new, and why the model still hallucinates even when the accurate data is right there.
2024 · Talk
HTMX is a different way to build web applications. No JSON or GraphQL, no serialization, no virtual DOM, no separate frontend deployment. You write HTML and pick whatever typed backend language you like. The talk builds an e-commerce shop with Kotlin, Spring Boot, and plain Tailwind to show what that looks like in practice.
2023 · Talk
2023 · Talk
Efficiency is one of the most misused words in IT. Say it and people immediately hear cost-cutting: fewer resources, less overhead, more automation. That reading was always too narrow, and in a world shaken by one crisis after another it stopped being enough. The talk is about building an IT department that gets stronger under stress, not just cheaper.
2023 · Talk
The TalentFormation Network rebuilds companies with the three-horizon model, and verticalization is the work horse for the first horizon: getting a company onto a solid base before it extends its business model. In practice that means building product and technology organizations along the lines of Team Topologies, with Self-Contained Systems mapped to the Business Model Canvas. All models are wrong, some are useful. Christoph and I explain which ones we combined and why.
2023 · Talk
There is no way around Single-Page Applications today. React, Angular, Vue, pick one, the standard answer for frontend architecture is a SPA. But the SPA idea is older than it looks. AngularJS shipped it broadly a decade ago. Hotwire takes a different route: clean architectures on low-level web standards, the UX you expect from a SPA, and loose coupling between teams, which is what keeps a frontend scalable.
2023 · Talk
Functional programmers tend to say "FP first". That purist stance does not fit the many real projects that are object-oriented and built on DDD, which is a shame, because those projects have plenty to gain from functional techniques. The talk follows a collaboration between BLUME 2000, firmly in OO hands, and Active Group, all FP purists, on a hexagonal DDD architecture in Kotlin: validation with applicative functors, free monads to separate the domain from the ports, and functional dependency injection.
2022 · Talk
Every company wants to be fast: fast into a new market, fast to ship a feature, fast to build a product. Time to market is the fuel for the build-measure-learn cycle, and running that cycle faster than your competitors is a real advantage. Wanting it is the easy part. The talk is about how you actually get there, and it comes down to independence and responsibility.
2022 · Talk
There is no way around Single-Page Applications today. React, Angular, Vue, pick one, the standard answer for frontend architecture is a SPA. But the SPA idea is older than it looks. AngularJS shipped it broadly a decade ago. Hotwire takes a different route: clean architectures on low-level web standards, the UX you expect from a SPA, and loose coupling between teams, which is what keeps a frontend scalable.
2022 · Talk
Kotlin advertises functional programming support, but in practice you have to reach for it deliberately. It is still easier than Java. A few of those techniques pay off when you build a clean architecture: reliable data organization and validation, flexible dependency injection with monads. They complement a DDD project well, and you can add them after the fact. The talk shows where functional programming earns its place in Kotlin.
2022 · Podcast
How do you create ideal working conditions in tech organizations, conditions that also give the organization a real competitive advantage?
2022 · Podcast
"Accelerate" gives CIOs a framework for implementing agile practices in a way that delivers measurable business success. As CIO of BLUME 2000, I did exactly that, and talk through the change process: the dos and don'ts, and practical tips for implementation.
2021 · Article
Speed, effectiveness, and joy through entrepreneurial responsibility.
2021 · Interview
Microservices are a big trend. But they get in the way of speed, and that is why something completely different is done at BLUME 2000: a full separation of business logic, organization, and finally technology. The interview describes how that works, alongside the talk on speed without microservices.
2021 · Article
The IT department of online retailer BLUME 2000 is meant to deliver new features faster. To achieve this, the traditional technical departments were reorganized into domain-specific teams and the IT landscape was split along domain lines.
2021 · Talk
There is no way around Single-Page Applications today. React, Angular, Vue, pick one, the standard answer for frontend architecture is a SPA. But the SPA idea is older than it looks. AngularJS shipped it a decade ago. The talk goes back to the frontend problems that led to SPAs in the first place, and asks whether we have better answers to those problems now.
2021 · Talk
Documentation matters at every company size. Developers still avoid it, because nobody wants to log into a second bloated tool to write it. So why not make docs feel more like writing code? Several markdown and asciidoc frameworks are open to developers and non-technical people alike, and they take a lot of friction out of the process. The talk tells our docs story: picking a framework and hosting it on GitLab Pages.
2021 · Talk
In the middle of the pandemic, BLUME 2000 started rebuilding its e-commerce platform. Remote mob programming and new ways of sharing knowledge let several teams ship the MVP in a few months. The talk covers the project setup, how iteratec supported the teams, the technology, and what we learned from one of Hamburg's more interesting e-commerce projects that year.
2021 · Talk
Plenty of companies jumped into microservices and single-page applications as if they solved everything, and ended up slowed down by infrastructure that got more complex instead of less. The talk shows the other route: good old HTML techniques, carefully cut macro services, and solid DevOps practices. The real point is that speed shows up when leadership, knowledge, organization, and technology pull in the same direction.
2020 · Talk
Omnichannel, digital business, verticalization, agile, apps. For a small or mid-sized company, the list alone is overwhelming. The talk is about how a company that size keeps pace with the big players, and now and then gets ahead of them.
2019 · Talk
Microservices and Spring Boot have become hard to separate. But Spring comes from a time of monoliths hosted on big on-premise servers, and a lot of its internals still carry that era with them. Serverless and DevOps change the requirements. Quarkus.io shows how lean and fast a web framework can be when it is designed for the way we work now. The talk sets up a few Quarkus services together and deploys them on Kubernetes.
2019 · Talk
Breuninger processed its product data with classic batch jobs for years. As business demands grew, batch stopped keeping up, so we rebuilt the pipeline around an event-driven design. The talk walks through that new pipeline with its trade-offs, built on Java 11, Kafka, MongoDB, and Atom feeds over HTTP and JSON.
2018 · Talk
2018 · Keynote
Verticalization, omnichannel, digital business, agile, apps, and in the middle of it a 136-year-old retailer you would not expect to find there. Breuninger is known for exquisite clothing, not for IT. In this keynote Katja Burkert, Head of Software Engineering, and I talk about the challenges and opportunities of vertical architecture, what makes code worth caring about, and why verticalization is crucial in software architecture.
2018 · Talk
Microservices are everywhere, and Self-Contained Systems have been gaining ground too. So how do the two concepts differ? Can you combine them sensibly, or are there contradictions and pitfalls to watch for? The talk answers that, and shows how both concepts play out in Breuninger's multi-channel platform.
2017 · Talk
The market is pushing online shops from one monolith toward a connected system of many microservices, all talking through interfaces. Clients inside and outside the shop, apps, IoT devices, phones, all expect real-time data. The iterative programming style we have been using runs into walls here. The talk digs into those problems, introduces reactive programming, and ends with code that streams data from database to frontend with Rx.
2017 · Talk
The market is pushing e-commerce from a closed shop toward an open ecosystem, and that means exposing functionality through an external API so native apps, social media, IoT devices, physical retail, and outside websites can all connect. The talk presents Breuninger's distributed microservice architecture, the motivation behind it, the practical lessons, and how we approached both public and internal APIs.
2017 · Talk
The market is pushing otto.de from a closed shop toward an open ecosystem, which means publishing shop functionality through an API so native apps, social media, IoT devices, and outside websites can all connect. The talk covers otto.de's microservice architecture and our external API, built with Java, Spring Security, and OAuth2, the challenges of distributed architectures, and a live demo of how quickly someone can build a surprising use case on top of the API.
2016 · Talk
In e-commerce the motto is more agile, faster, more innovative, and staying successful means questioning your business model regularly. otto.de is one of Germany's largest e-commerce platforms. It runs on a strict, vertically cut shared-nothing architecture, and to avoid sliding back into the problems of monoliths, we build it as microservices and rebuilt the infrastructure to match. The talk covers that architecture and, just as much, how you actually handle microservices day to day.
Current topics, formats, and the speaker bio are on the home page. The best invitations name the audience, the format, and the one question you want people to leave thinking about.