SOLID (object-oriented design)

In computer programming, SOLID (single responsibility, open-closed, Liskov substitution, interface segregation and dependency inversion) is a mnemonic acronym introduced by Michael Feathers for the “first five principles” named by Robert C. Martin[1][2] in the early 2000s[3] that stands for five basic principles of object-oriented programming and design. The intention is that these principles, when applied together, will make it more likely that a programmer will create a system that is easy to maintain and extend over time.[3] The principles of SOLID are guidelines that can be applied while working on software to remove code smells by providing a framework through which the programmer may refactor the software’s source code until it is both legible and extensible. It is part of an overall strategy of agile and Adaptive Software Development.[3]

Initial	Stands for	Concept
S	SRP[4]	Single responsibility principle a class should have only a single responsibility (i.e. only one potential change in the software’s specification should be able to affect the specification of the class)
O	OCP[5]	Open/closed principle “software entities … should be open for extension, but closed for modification.”
L	LSP[6]	Liskov substitution principle “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.” See also design by contract.
I	ISP[7]	Interface segregation principle “many client-specific interfaces are better than one general-purpose interface.”[8]
D	DIP[9]	Dependency inversion principle one should “depend upon abstractions, [not] concretions.”[8]

https://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29

YAGNI:
https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it