Clean Architecture: Why? How? For Whom?
summary
Presentation explaining the principles and motivations behind the Clean Architecture pattern, why teams should adopt it and who benefits. It describes how to apply Clean Architecture in software projects—separating concerns, using dependency rules and layers—and targets developers and architects looking for maintainable, testable codebases.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10Clean Architecture origin
- 2:55Problems with messy architectures
- 10:20Dependency on libraries
- 17:43Hexagonal architecture explained
- 20:10Use Cases (New Skies) core
- 25:11Use Cases structure files
- 30:09MVP and View Models view
- 33:59Clean Architecture full flow
- 37:53Separation of concerns tests
- 41:26When to apply Clean Architecture
- 42:10Framework advice pragmatism
- 43:15Q&A
related talks
51mClean Architecture: A Deep Dive
56mClean Architecture: Deep Dive
19mClean Architecture: A Solution to Improve System Maintainability
06mIs Clean Architecture Possible in My Company?
47mStep by Step Toward Clean Architecture
43mAgile clean architecture
55mClean architecture that harms your code
25mKeynote: Step by Step Towards Clean Architecture