Just started course, Design Patterns in JavaScript on Udemy.
Here is summary from first section by @nesteruk from course.
- A class should only have one reason to change
- Seperation of concerns -> different classes handling different, independet tasks/problems
- Clases should open for extensions but closed for modification
- You should be able to substitute a base type for a subtype
- Don't put too much into an interface; split into separate interfaces
- YAGNI - You Ain't Going to Need It
- High-level modules should not depend upon low-level ones; use absractions
Top comments (0)