BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

Software Engineering

166Separation of Concerns
167Abstraction and Information Hiding
168Don't Repeat Yourself (DRY)
169Keep It Simple, Stupid (KISS)
170You Aren't Gonna Need It (YAGNI)
171Encapsulation and Data Hiding
172Program to an Interface, Not an Implementation
173Favor Composition Over Inheritance
174The Principle of Least Knowledge (Law of Demeter)
175Command-Query Separation
176Fail Fast and Defensive Programming
177Understanding Coupling: How Components Depend on Each Other
178Types of Coupling: From Tight to Loose
179The Cost of Tight Coupling
180Understanding Cohesion: What Belongs Together
181Types of Cohesion: From Weak to Strong
182The Relationship Between Coupling and Cohesion
183Measuring Coupling and Cohesion in Practice
184Refactoring to Reduce Coupling
185Refactoring to Increase Cohesion
186Why Software Must Be Designed for Change
187Anticipating Change vs. Over-Engineering
188Stable Interfaces and Implementation Flexibility
189Dependency Direction and Stability
190Extensibility Through Abstractions
191Configuration and Parameterization
192Plugin Architectures and Extension Points
193The Cost of Flexibility

Software Engineering

166Separation of Concerns
167Abstraction and Information Hiding
168Don't Repeat Yourself (DRY)
169Keep It Simple, Stupid (KISS)
170You Aren't Gonna Need It (YAGNI)
171Encapsulation and Data Hiding
172Program to an Interface, Not an Implementation
173Favor Composition Over Inheritance
174The Principle of Least Knowledge (Law of Demeter)
175Command-Query Separation
176Fail Fast and Defensive Programming
177Understanding Coupling: How Components Depend on Each Other
178Types of Coupling: From Tight to Loose
179The Cost of Tight Coupling
180Understanding Cohesion: What Belongs Together
181Types of Cohesion: From Weak to Strong
182The Relationship Between Coupling and Cohesion
183Measuring Coupling and Cohesion in Practice
184Refactoring to Reduce Coupling
185Refactoring to Increase Cohesion
186Why Software Must Be Designed for Change
187Anticipating Change vs. Over-Engineering
188Stable Interfaces and Implementation Flexibility
189Dependency Direction and Stability
190Extensibility Through Abstractions
191Configuration and Parameterization
192Plugin Architectures and Extension Points
193The Cost of Flexibility

← Software Engineering

Lesson 186 of 1,933·5. Software Design PrinciplesPro lesson

Why Software Must Be Designed for Change

Understanding that change is inevitable in software and why designing for it reduces cost and risk over time.

This lesson is for subscribers

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

See pricing Back to course