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 specific technical solution, they're usually operating from an underlying value or concern that they haven't made explicit. Before evaluating technical options, dig into what's driving the strong preference. Is it fear of...
by Organisers @virtualddd | Mar 1, 2026
When choosing an architectural approach, explicitly think through what it means for the teams that deploy, test, and support your software—not just what it means for developers. Introducing patterns like message queues or event sourcing changes how QA needs to test...
