software design principles

SOLID

1. Single Responsibility Principle
   • A class with only the first single responsibility
2. Open-Closed Principle
   • For extension development, closed for modification.Module design considerations: Implement changes to the module's behavior without modifying the source code.
3. Liskov Substitution Principle
   • Subclass design should ensure that subclasses can appear wherever the base class appears
4. Interface Isolation Principle
   • Classes shouldn't be forced to depend on methods they don't use, that is, an interface should have as little behavior as possible, is it lean, and is monolithic?
5. Dependency Inversion Principle
   • High modules do not depend on low modules, they all depend on abstraction.Abstraction does not depend on details, details depend on abstraction?

switch statement
If it is an object-oriented language, consider using polymorphism instead.
If it is a procedurally oriented language, consider refactoring with table-driven or strategy patterns.