[Explained] What is a SOLID Code ? Is it necessary?

[cr.Sensei]

Hello everyone! I'm Sensei. I have been coding since 2015 and working as Senior Full-Stack Developer.

I am here to give some information to our friends who are known by software developers working in many companies today, but who stepped into this new world with their own efforts.SOLID simply means good and understandable code.


S — Single-responsibility principle

A class (object) can only be changed for one purpose, which is the responsibility imposed on that class, meaning that a class (which can also be reduced to a function) has only one job to do.

O — Open-closed principle

A class or function should preserve existing properties and not allow changes. That is, it should not change its behavior and should be able to acquire new features.

L — Liskov substitution principle

We should be able to use subclasses instead of the (superior) classes from which they derive, without needing to make any changes in our code.

I — Interface segregation principle

Instead of gathering all the responsibilities into a single interface, we should create more customized interfaces.

D — Dependency Inversion Principle


Dependencies between classes should be as low as possible, especially high-level classes should not depend on lower-level classes.