Modularity, Modules as Knowledge Boundaries, and Abstractions

#188 - Balancing Coupling in Software Design: Principles for Modular Software - Vladik Khononov

Topic 5 of 9

Published Aug 26, 2024 · Clip 22:45–36:26 (13:41)

Vlad critiques recursive and Lego-brick definitions of modularity, proposing instead that a modular system is one designed to support future, reasonable goals. He distinguishes modules from components, noting that historically modules encapsulate behavior, expose an interface, and have the potential to be independently compiled. He explains that modules are knowledge boundaries, using an encryption example to show how encapsulating knowledge in a module avoids duplication and cascading changes. He contrasts this with ineffective abstractions like DTOs that merely copy identical data structures without hiding knowledge, adding cognitive load and accidental complexity instead.