SOLID Principles in Practice: Clean Architecture
summary
Clean Architecture (from Robert C. Martin) and the SOLID principles are explained with a focus on improving testability by separating application logic from external dependencies. A practical example shows how to apply SOLID in real code, with particular attention to the D—dependency inversion—demonstrating how to decouple modules from external components to make them easier to test.
AI-written summary · about
chapters (17)
- 0:00SOLID and Clean intro
- 10:43SOLID origins
- 11:53Single Responsibility
- 12:37Open/Closed Principle
- 13:23Liskov risks
- 14:51Interface Segregation benefits
- 16:20Dependency Inversion deep dive
- 19:11Dependency inversion in modules
- 21:01Clean Architecture modules
- 22:28Layered architectures compared
- 23:58Dependency rule
- 25:05Framework independence
- 26:30Conventions vs rules
- 27:39Testing domain logic
- 29:07Architecture pitfalls
- 30:39Further learning
- 32:09Q&A
related talks
47mSOLID Object-Oriented Design
01h 00mSOLID Revisited : The State of the Matter
43mWhat Comes After SOLID? Seeking Holistic Software Quality
19mClean Architecture: A Solution to Improve System Maintainability
06mIs Clean Architecture Possible in My Company?
51mA Contrarian View of Software Architecture
24mKeynote – Michael Feathers
01h 34mThe Intersection of Architecture and Implementation