
Essential vs Accidental Complexity

#188 - Balancing Coupling in Software Design: Principles for Modular Software - Vladik Khononov
Topic 4 of 9
Published Aug 26, 2024 · Clip 19:36–22:45 (3:09)
Vlad explains essential complexity as the complexity inherent in a non-trivial business domain, which cannot be avoided and must be managed with tools like DDD and design patterns. Accidental complexity, by contrast, is introduced by poor design, making it impossible to predict the effect of changes on other components. He emphasizes that design of interactions—coupling between components—determines whether accidental complexity is introduced or essential complexity is managed. The host recaps that coupling is a root cause of accidental complexity.