Co-organizer of the DDD Paris user group, Thomas is an eXtreme Programmer & technical architect obsessed by use cases (Vs. solution-driven approaches). He likes using DDD & TDD to boost his efficiency at work. Advocating the advantages of the Hexagonal architecture for many years (talks, blogposts...), Thomas has also live-coded with Alistair Cockburn on that topic.
Creating multiple models for the same problem is one of the more important lessons that Domain Driven Design teaches us. It is a lot cheaper to quickly iterate over them and throw away less useful prototypes before we even start coding. However, creating multiple models can be hard. When we begin gaining insight from our domain, we suffer a lot from cognitive biases that get in our way to gain new insights. We need these insights before we even start thinking about modelling. Tools like event storming and example mapping can help us to deliberate discover, and battle these biases. They help you quickly gain insight into the problem space. But the fallacy here is that we can get locked into the tool, and get stuck again? Read more...
Technical Debt Detective
Inventor of EventStorming
UX person in love with DDD
Author of Idea Flow
Data Horticulturist. Code Tinkerer.
Development Manager and Architect
Domain Driven Developer
Ask Me About Dojos
Developer, Crafty Person, and Eater of Legacy Spaghetti
Author of “Domain-Driven Design”
Event-driven Model Enthusiast
Engage and Embrace
Student of Systems
Engineering Excellence Evangelist
Junior Master Strategist
Author and Obsessive Programmer
Functional Domain Modeler
Distributed engineer, AFOL