SOLID Principle: Theory and Implementation in Swift

This is a series about the SOLID principles introduced by Uncle Bob (Robert C. Martin). SOLID is a set of design principles that help us write code that is easier to understand, maintain, and evolve over time. SOLID consists of five principles: S - Single Responsibility Principle read here : https://dev.to/cakoko/single-responsibility-principle-srp-theory-and-implementation-in-swift-3f83 O - Open Closed Principle L - Liskov Substitution Principle I - Interface Segregation Principle D - Dependency Inversion Principle Each of these principles tries to solve a different kind of design problem, but they all share the same goal: helping us write code that stays manageable as the system grows. Why I’m Writing This Series This article series is created while I’m working on my other series: What I’m Learning About Writing Better Structured Code While writing that series, I realized something. Many of the ideas I want to explain are closely related to SOLID. But explaining them properly require