Pergunta comum em entrevista de SOLID & Design Patterns. A resposta abaixo está em inglês, do jeito que dá para falar numa entrevista: leia, feche e tente explicar com as suas palavras.
Five design principles for reasoning about change and contracts, not a guarantee of scalable software.
Single Responsibility: a module has one reason to change, tied to the actor or policy it serves. It does not mean one method per class.
Open/Closed: design stable boundaries so expected extensions do not require changing every caller. New requirements can still require modifying existing code.
Liskov Substitution: a subtype must preserve the behavior promised by its supertype, including accepted inputs and guarantees.
Interface Segregation: clients should not depend on methods they do not use.
Dependency Inversion: high-level policy and low-level details depend on suitable abstractions, rather than policy being coupled to a concrete detail.
Example: a shipping adapter must preserve currency, units, and failure behavior. Sharing a method name is not enough to make two providers substitutable.
Ler é o primeiro passo. No app, essa pergunta vira flashcard com repetição espaçada, e o módulo tem quiz e simulado para testar o que ficou.
Treinar essa pergunta no app