Tell about each of the SOLID principles.

The SOLID principles are five fundamental principles of object-oriented programming that help create flexible, extendable, and maintainable code:

1. Single Responsibility Principle (SRP) — the principle of single responsibility. Each class should have only one reason to change, meaning it should be responsible for one specific task.

2. Open/Closed Principle (OCP) — the principle of openness/closure. Software entities should be open for extension but closed for modification.

3. Liskov Substitution Principle (LSP) — Barbara Liskov's substitution principle. Subclass objects should be interchangeable with superclass objects without violating the correctness of the program.

4. Interface Segregation Principle (ISP) — the principle of interface segregation. Clients should not depend on interfaces they do not use; it is better to create several specialized interfaces than one universal interface.

5. Dependency Inversion Principle (DIP) — the principle of dependency inversion. High-level modules should not depend on low-level modules; both should depend on abstractions. Abstractions should not depend on details; details should depend on abstractions.

Applying these principles in Go helps create a clean architecture and facilitates support and extension of the code.