Architecture Insights
Alan and Joe discuss the importance of substituting parts in architecture without polluting it with unnecessary dependencies. Joe highlights the Interface Segregation Principle, emphasizing the need to avoid making classes depend on unnecessary interfaces, preventing tight coupling and making it easier for callers to interact with the system.In this clip
From this podcast
Coding Blocks
Clean Architecture - Programming Paradigms
Related Questions
What needs to be done with business logic in the data layer that doesn't make sense to have in the domain layer according to Uncle Bob's clean architecture in the episode Clean Architecture - The Art of Drawing Lines and the clip Clarifying Dependencies?
Should the data layer contain logic according to Uncle Bob's Clean Architecture in the episode Clean Architecture - The Art of Drawing Lines and the clip Clarifying Dependencies?