DDD Methods for Day to Day Problem Solving
(This is a hands-on lab with limited capacity)
"It is not the domain experts knowledge that goes into production; it is the assumption of the developers that goes into production". This famous quote from Alberto Brandolini is very accurate, and it points in the right direction: we need to bring domain knowledge into our decisions and our software to offer the best solution in the given context.
One of the reasons why software solutions become messy and hard to maintain is that we tend to jump to solutions before really understanding the problem. They may work out for now, but how do we ensure that they will fit in the future? This is where the paradigm of Domain-driven Design can help us out: DDD gives us the option to change our model when the business is changing. The workshop is not only for engineers but for everyone involved in product development.
In these two hours, we will dissect a business problem and experience how to solve it by using various techniques and tools in the day-to-day business. We will learn how to ensure that our decisions and implementations are driven by the Domain, which pitfalls to avoid and which principles to follow. After the workshop, every participant should have a good idea of how to start using the techniques and tools at work.
- About Krisztina Hirth
Hrmony GmbH - Berlin - Coding Architect TwitterLinkedInBlog
Software developer for almost 20 years, always looking for the right way to deliver reliable, resilient and expandable value, either by software or by knowledge. I have worked in all kinds of teams, mainly in an agile manner, always looking for improvements and ways to reach these. In my book, agility is nothing else as feedback-driven development, which should be lived by the whole organization to succeed in the market - financially and regarding the people making it possible.