Accidental complexity is the extra difficulty and disorder introduced by design choices, shortcuts, and brittle abstractions—not by the problem itself. It appears when a simple change spreads across files or unrelated tests break. section 1.0
Hard-wiring lets changes ripple between parts of a system:
- Framework, database, interface, and service dependencies become coupled to the application. section 1.0
- Database choices leak into business logic, transport models become domain models, and local shortcuts constrain other components. section 1.0
Hexagonal Architecture contains these ripple effects with explicit boundaries: the core defines what it needs, while replaceable adapters connect external technologies. Dependencies point inward, keeping domain logic framework-agnostic and testable in isolation. section 1.0 section 1.6

