Today programmers do not develop applications from scratch but they spend their time fixing, extending, modifying and enhancing existing applications. The biggest problem in their daily work is that with time maintenance mutates from structured programming to defensive programming: The code becomes too complex to be maintained. We put in code we know is stupid from an architectural point of view but it is the only solution that will hopefully work. Maintenance is more and more difficult and expensive. Our software accumulates technical debts.
In this talk, I will show you how Domain-Driven Design can help you and your teams to avoid this apparently inevitable dead end. The concepts and solutions of DDD can be applied at the beginning of a project but will also improve the situation in an ongoing project or during maintenance.
Escaping the Enshittification Trap: Systems Thinking for Sustainable Quality
7pm New Zealand time, please check the event time in your time-zone. In this talk, we’ll explore quality as an emergent property of our teams, tools, and processes—not just something we test at the end. We’ll look at challenges like speed to market and...
