Composition over inheritance is a design principle that is gaining increasing popularity in the world of software development. It recommends using composition, which involves combining simple objects to form more complex ones, over inheritance, which involves inheriting properties and behaviors from a parent class. In this article, we will discuss…
The Law of Demeter is a software design principle that states that a module should not know about the inner workings of the objects it manipulates. In other words, a module should only communicate with its immediate neighbors and not with the objects that they manipulate. This principle is also…
You Ain’t Gonna Need It (YAGNI) is a software development principle that suggests that software developers should only add features or functionality that are necessary for the current requirements of the application. The principle encourages developers to avoid adding unnecessary features or functionality that may be needed in the future…
The Keep It Simple Stupid (KISS) principle is a design principle that advocates for simplicity in software design and development. The principle states that systems should be designed and developed in the simplest way possible, without unnecessary complexity or features. The KISS principle emphasizes the importance of simplicity in software…
The Don’t Repeat Yourself (DRY) principle is a software development principle that aims to reduce duplication in code. The basic idea behind DRY is that every piece of knowledge should have a single, unambiguous representation within a system. This can help reduce errors, simplify maintenance, and make code easier to…
Single Responsibility Principle Each class should have only one responsibility By looking at the line of codes, we could probably somehow measure how many responsibilities actually lie in the class. With that, I am taking different examples from different sources to better help us measure how many lines of codes…
Open-Closed Principle Class should be opened for extension but closed for modification This principle promotes writing a maintainable code by having two important characteristics: Open for extension Closed for modification In short, you should be able to add almost any new feature to your class easily and will not have…
Liskov Substitution Principle Child class should not break the parent class type definitions A subclass should be able to override the parent class method in a way that it doesn’t break the functionality of the base class.The benefit of this principle is that when code is interchangeable, it becomes more…
Interface Segregation Principle Implement only what you need By segregating our interface, we solve the FAT interface problems. FAT as in when an interface has too many methods that contain more information than we really needed to use. Simply put, we sometimes only use some instead of everything we have.…
Dependency Inversion Principle Depend on abstractions, not on concretions High-level modules should not depend on low-level modules. With this theory, high level modules like the view controller, should not depend directly on low level things, like a networking component. Instead, it should depend on abstractions or in Swift term, protocol.…