by Organisers @virtualddd | Mar 1, 2026
Before committing to a major architectural change, explicitly map it against the concrete frustrations that make the team's job difficult. A proposed solution might use modern technology but still leave developers dealing with the same unpleasant work. If the new...
by Organisers @virtualddd | Mar 1, 2026
When someone pushes hard for a particular architectural approach, they're often expressing underlying values or fears rather than purely technical reasoning. By explicitly identifying these value-based heuristics—the principles actually driving their...
by Organisers @virtualddd | Jan 20, 2026
Treat testability, observability, and recoverability as first-class design concerns, not afterthoughts. A system that cannot be easily tested, understood in production, or quickly restored is inherently low-quality. Build in the necessary instrumentation, APIs, and...
by Organisers @virtualddd | Jan 20, 2026
Shift focus from attempting to eliminate every bug before deployment to ensuring rapid recovery from failure in production. The cost of a quickly remediated production incident is often lower than the cost of maintaining complex, slow, and brittle pre-production...
by Organisers @virtualddd | Jan 19, 2026
Deliberately remove the legacy system from the immediate scope of discussion. Redirect the conversation to the underlying business problems the system is meant to solve, fostering a solution-agnostic perspective. Example To move beyond discussions of 'message...
