Solid principles are a way, a set of recommendations and principles, to build robust software. SOLID principles work for object-oriented design (OOP). Their author is Robert C. Martin and date from around 2000.
A quick overview
| ||Single responsibility principle||Each class has just one responsibility.|
| ||Open/Closed principle||The functionality of a class can be extended without modifying it.|
| ||Liskov substitution principle||Classes must be fully substitutable by their descendants.|
| ||Interface segregation principle||Use small and narrowly focused interfaces.|
| ||Dependency inversion principle||Depend on abstractions, not on implementations.|
Jan Barášek More about the author
The author works as a senior developer and software architect in Prague (Czech republic, Europe). He designs and manages large web applications that you know and use. Since 2009 he has gained a wealth of experience which he passes on through this website.
I'd be happy to help:Contact