BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

Software Engineering

194What is the Single Responsibility Principle
195Identifying Multiple Responsibilities
196The Axis of Change Concept
197Cohesion and SRP
198Refactoring to SRP: Extracting Classes
199SRP at Different Levels
200Common SRP Violations and Fixes
201Understanding the Open/Closed Principle
202Why Modification is Risky
203Extension Through Inheritance
204Extension Through Interfaces and Polymorphism
205The Strategy Pattern and OCP
206When to Apply OCP
207Balancing OCP with Simplicity
208What is the Liskov Substitution Principle
209Behavioral Subtyping and Contracts
210LSP Violations: Strengthening Preconditions
211LSP Violations: Weakening Postconditions
212The Rectangle-Square Problem
213Avoiding LSP Violations with Composition
214LSP and Exception Handling
215Interface Segregation Principle: No Client Should Depend on Unused Methods
216Fat Interfaces and Their Problems
217Splitting Interfaces by Client Needs
218Role Interfaces and Interface Segregation
219ISP and Language Features: Abstract Classes vs Interfaces
220Balancing ISP with Interface Proliferation
221What is the Dependency Inversion Principle
222Abstractions Should Not Depend on Details
223Inverting Dependencies with Interfaces
224The Dependency Flow vs Control Flow
225DIP and Dependency Injection
226Benefits of Dependency Inversion
227Recognizing DIP Violations

Software Engineering

194What is the Single Responsibility Principle
195Identifying Multiple Responsibilities
196The Axis of Change Concept
197Cohesion and SRP
198Refactoring to SRP: Extracting Classes
199SRP at Different Levels
200Common SRP Violations and Fixes
201Understanding the Open/Closed Principle
202Why Modification is Risky
203Extension Through Inheritance
204Extension Through Interfaces and Polymorphism
205The Strategy Pattern and OCP
206When to Apply OCP
207Balancing OCP with Simplicity
208What is the Liskov Substitution Principle
209Behavioral Subtyping and Contracts
210LSP Violations: Strengthening Preconditions
211LSP Violations: Weakening Postconditions
212The Rectangle-Square Problem
213Avoiding LSP Violations with Composition
214LSP and Exception Handling
215Interface Segregation Principle: No Client Should Depend on Unused Methods
216Fat Interfaces and Their Problems
217Splitting Interfaces by Client Needs
218Role Interfaces and Interface Segregation
219ISP and Language Features: Abstract Classes vs Interfaces
220Balancing ISP with Interface Proliferation
221What is the Dependency Inversion Principle
222Abstractions Should Not Depend on Details
223Inverting Dependencies with Interfaces
224The Dependency Flow vs Control Flow
225DIP and Dependency Injection
226Benefits of Dependency Inversion
227Recognizing DIP Violations

← Software Engineering

Lesson 222 of 1,933·6. SOLID PrinciplesPro lesson

Abstractions Should Not Depend on Details

Learning why abstractions must be stable and independent of concrete implementation details.

This lesson is for subscribers

You've completed the free preview. Subscribe to unlock every lesson in every course.

See pricing Back to course