Présentation par : Cyrille MARTRAIRE (Arolla)
📕 Résumé :
Je lis des publications scientifiques tout le temps, pour n'importe quel sujet que je veux apprendre sérieusement. Pourquoi perdre son temps à lire des opinions et des résumés superficiels quand vous pouvez trouver des réponses fiables et précises directement dans des publications scientifiques ? Mais on ne va pas se mentir, la littérature académique peut paraître intimidante si vous ne savez pas comment l'aborder. Et même avec l'IA, la lecture d'articles reste un ingrédient clé.
Si vous n'êtes pas familier avec l'univers des publications scientifiques, rejoignez-moi pour découvrir comment explorer ces contenus austères mais fascinants propulsera votre apprentissage, quel que soit le sujet. Nous illustrerons cela à la fois pour modéliser un domaine métier (à la DDD) et pour comprendre le groove en musique (pour le fun).
Enregistré en avril 2026 à Paris, Palais des Congrès, Porte Maillot.
Une liste de papiers sélectionnés par Cyrille dans le domaine de l'informatique pour commencer https://gist.github.com/cyriux/ee0d382bda9853e3fe86189f4f95658f
If you like this Kata, check out another Kata I’ve published using the example of an online car dealership: https://medium.com/nick-tune-tech-strategy-blog/architecture-ddd-kata-online-car-dealership-540c534121e2
If you would like to learn or practice how to break up a large business into domains and use them as the foundation for your software architecture and team organization, I have created a strategic domain-driven design kata that you may find useful. It’s based on the industry of online takeaway ordering and delivery using a fictitious business called Delivericious.
You can find the Miro board here: https://miro.com/app/board/o9J_l45tkpU=/
Software teams often reach for Kubernetes or similar prepackaged answers as default solutions to complex problems. But Kubernetes isn’t a strategy—it’s a tool. Using it prematurely can bury your team in unnecessary complexity and unwanted consequences. These ‘default’ answers reflect a deeper issue: we don’t understand the problem we're solving.
Through real-world examples, we’ll discuss how to think critically about the way decisions are being made in your company. We’ll introduce concepts like participation theater—when people perform the rituals of decision-making without making real decisions—alongside problem restatement as a tool to uncover the real challenge at hand. We’ll also examine different types of decisions (reactive vs. proactive, reversible vs. irreversible) and why recognizing them early changes how you should approach them.
This talk is a call to slow down to speed up your decision-making. Whether you're an engineer, architect, or tech lead, this session will challenge you to pause before reaching for Kubernetes (or other technologies) and instead ask: what problem am I really trying to solve?
About Gien
Gien Verschatse is an experienced consultant and software engineer that specialises in domain modelling and software architecture. She has experience in many domains such as the biotech industry, where she
specialised in DNA building. She's fluent in both object-oriented and functional programming, mostly in .NET. As a Domain-Driven Design practitioner, she always looks to bridge the gaps between experts, users, and engineers.Gien is studying Computer Science at the OU in the Netherlands. As a side interest, she's researching the science of decision-making strategies, to help teams improve how they make technical and organisational decisions. She shares her knowledge by speaking at international conferences.And when she is not doing all that, you'll find her on the sofa, reading a book and sipping coffee.