BackendGeneralTable-stakes
SOLID Principles
Also written as SOLID
Five classic guidelines for writing object-oriented code that's easier to change: each class has one job, code is extended rather than edited, and parts depend on interfaces rather than specifics.
Think of it like
Workshop rules for tidy tools: each tool does one job, and every tool fits the standard mounts.
Junior or senior?
A staple of interview prep, especially in Java and .NET hiring. Reciting the five letters is easy; senior candidates give a real example of applying (or deliberately breaking) one.
Ask them
“Give me an example from your code where following one of the SOLID principles made a later change easier.”