Do you check for adherence to SOLID principles during code reviews?

Yes, during code review it is important to check adherence to SOLID principles, as they help create flexible, maintainable, and extendable code.

Especially in iOS development (Swift/Objective-C), SOLID principles help:

• Single Responsibility Principle (SRP): a class or structure should have one responsibility, which makes testing and maintenance easier.
• Open/Closed Principle (OCP): code should be open for extension but closed for modification, reducing the risk of errors when adding new features.
• Liskov Substitution Principle (LSP): subclasses should correctly replace base classes without breaking logic.
• Interface Segregation Principle (ISP): it is better to have several specialized interfaces than one general one.
• Dependency Inversion Principle (DIP): dependencies should be based on abstractions, not on concrete implementations.

When reviewing, pay attention to:

• Avoiding large classes with many responsibilities.
• Using protocols (interfaces) to separate responsibilities.
• Correct inheritance and method overriding.
• Dependency injection to improve testability.

This helps maintain code quality and facilitates team collaboration.