By drawing boundaries around your business logic and using Dependency Inversion, you stop writing "framework-dependent code" and start writing
The act of architecture is defined as the act of drawing lines called . These lines separate elements that change for different reasons and at different rates (Single Responsibility Principle) from one another. Martin details when to draw these lines (usually early, to prevent coupling) and when to ignore them (YAGNI—You Aren't Gonna Need It) to avoid over-engineering. arquitectura limpia robert c martin pdf