
Domain-Driven Design and Project Failures

#76 - Learning Domain-Driven Design - Vladik Khononov
Topic 3 of 12
Published Feb 14, 2022 · Clip 13:48–17:35 (3:47)
Vladik expands DDD as 'business domain-driven software design': software design equals a function of the business domain. Wrong domain knowledge leads to wrong strategic decisions (components, communication, team allocation) and tactical decisions (patterns, business logic implementation). The host asks whether DDD can solve the software crisis of ~50% failing projects; Vladik argues most failures trace to communication issues, and DDD's core principle—building shared understanding via a ubiquitous language—reduces rework and wrong assumptions.