Step by Step Toward Clean Architecture
summary
Practical guidance for improving an existing codebase toward Clean Architecture using small, low-risk changes that any developer (not just architects or leads) can introduce. It names iterative refactorings and design adjustments that most effectively spread better structure across classes, packages, and artifacts, and discusses their risks and how quickly they propagate positive effects—useful when releases and limited refactoring windows constrain work.
AI-written summary · about
chapters (8)
- 0:00Clean architecture intro
- 12:42Visualizing dependencies
- 22:27Interactive quiz
- 26:22System boundaries
- 31:24Layered to domain architecture
- 33:11Avoiding code duplication
- 38:28Strong typing and object IDs
- 42:22Dependency inversion
related talks
56mClean Architecture: Deep Dive
51mClean Architecture: Why? How? For Whom?
51mClean Architecture: A Deep Dive
55mClean architecture that harms your code
06mIs Clean Architecture Possible in My Company?
19mClean Architecture: A Solution to Improve System Maintainability
23mClean Architecture? Clean Code? Refactoring? Tests? What does this change in my code?
43mAgile clean architecture