SOLID / DRY principles

In software development, Object-Oriented Design plays a crucial role when it comes to writing flexible, scalable, maintainable, and reusable code. There are so many benefits of using OOD but every developer should also have the knowledge of the SOLID principle for good object-oriented design in programming.


The SOLID principles are designed to help developers design robust, maintainable applications.

The five SOLID principles are:
Single-responsibility principle - Function and classes should have one job.

Open–closed principle - Classes and functions should be open for  extension but not for modification.

Liskov substitution principle - Child class can replace parent class

Interface segregation principle - This principle is the first principle that applies to Interfaces instead of classes in SOLID and it is similar to the single responsibility principle. It states that “do not force any client to implement an interface which is irrelevant to them“. Here your main goal is to focus on avoiding fat interface and give preference to many small client-specific interfaces. You should prefer many client interfaces rather than one general interface and each interface should have a specific responsibility.

Dependency inversion principle -High-level modules/classes should not depend on low-level modules/classes. Both should depend upon abstractions.

DRY principle
The DRY (don't repeat yourself) principle is a best practice in software development that recommends software engineers to do something once, and only once.

Comments

Popular posts from this blog

Difference between localStorage and sessionStorage

Scope in javascript

What is memoization