Language and Events

We're back with another exciting evening of talks — two speakers, two great topics, and plenty of time to connect over food and drinks. Whether you're deep into architecture or just getting started, there's something for everyone!

***

Talk 1: Talk the Talk and Walk the Walk with a Living Language Chris Simon — Software Engineer, Australia joining us live
Language isn't just syntax — it's the foundation of how we think and communicate about our systems. In this talk, Chris explores what it really means to work with a living ubiquitous language: one that evolves alongside your domain, stays consistent across code, documentation, and conversations, and actually reflects how the business works. A practical and thought-provoking look at keeping language alive in your codebase and your team.

Chris is a technology coach and advisor helping technology teams drive business success. He has a particular focus on helping startups realize their vision and new CTOs flourish in their roles. He also supports executives & boards with strategic technology advice, and engineering teams with training, mentoring, and consulting in architecture, quality, domain-driven design, and test-driven development.
He is a regular meetup & conference speaker (https://chrissimon.au/speaking/) and to support teams using Domain-Driven Design, he recently launched https://contextive.tech & co-founded the DDD Australia meetup.
He is the technical co-founder of https://www.inloop.com.au, home of Australian Fintech success stories https://www.flexischools.com.au and https://www.lanternpay.com (recently acquired by NAB).

***

Talk 2: SOLID API Evolution
Matthias Kolb - Software Consultant
The SOLID principles are considered best practice in object-oriented programming for building maintainable and flexible software.
APIs play a central role in modern MACH architectures: they represent core business capabilities and reflect externally how well both the software and the organization meet these quality goals.
We apply SOLID principles to agile API design, adopt the client perspective, and explore the constraints and opportunities for the continuous evolution of public APIs.
Using concrete DOs, DON’Ts, and DEPENDs for semantic versioning of OpenAPIs, we demonstrate how API designers can enable sustainable API evolution.

***Matthias ***is a physicist and a former entrepreneur in LED technology. Over the past ten years, he has worked as a freelance Senior Software Engineer and Software Architect for clients across various industries, including healthcare, automotive, and the public sector. He values the intellectual and linguistic insights of Domain-Driven Design, Clean Code, and Clean Architecture. He is currently supporting a major German health insurance company in its domain-driven transformation.

***

Talk 3: 🚀 Fast Prototyping in Domain Storytelling — From Workshop to Working UI in Minutes
You've just run a great Domain Storytelling workshop. The Miro board is full of actors, activities, and work objects. Everyone nodded. Great session.
Then Monday arrives — and the board gets bookmarked. Nothing changes.
Sound familiar? In this talk, I'll show you how to close that gap fast — using the artifacts your workshop already produced.
What you'll learn:
Domain Storytelling gives you two powerful outputs: the Domain Story (who does what, in what order) and the Visual Glossary (the shared vocabulary of the domain). Together, they map almost directly onto the building blocks of a software prototype — screens, entities, user flows, and button labels.
I'll walk you through how to hand those artifacts to an AI and generate a clickable HTML prototype during the workshop itself — not a week later when the energy has faded.
We'll look at a real example: a bike-sharing system built live from a ten-step Domain Story and a six-term Visual Glossary. The prototype was ready before the session ended — and it immediately surfaced edge cases nobody had named: a race condition between booking and arrival, a distinction between "code confirmed" and "lock actually closed", and a business rule about single-use codes hiding a potential bug.
Why it works:
A Domain Story asks, "What do you want to do?" A prototype asks, "Is this what you meant?" These are different questions — and they surface different answers. Domain experts stop being narrators and start being critics. That shift is where the real value is.

📖 Curious already? Read the full blog post here: 👉 https://www.codecentric.de/en/knowledge-hub/blog/from-domain-story-to-prototype
See you there! 👋

***Annegret ***is Chief Software Architect at codecentric AG, with over 30 years of experience in software development. She has worked across a wide range of roles — developer, product owner, architect — and industries including automotive, insurance, logistics, and financial services.
Her passion lies at the intersection of Domain-Driven Design, microservices, and API design. She is the co-author of Crafting Great APIs with Domain-Driven Design and a regular speaker at international conferences on software architecture and collaborative modeling.

***