In part 4 of the SOLID series, we continue the discussion of decoupling and how to avoid so-called 'interface pollution', wherein classes are unnecessarily forced to implement behaviors that they don’t need. It is here that our next SOLID principle appears: the Interface Segregation Principle.
In part 2 of the SOLID series, we discuss what happens when an object needs to change. As with responsibility changes, this poses a challenge for the maintenance of downstream objects that could inadvertently be affected by the change. One way to reduce the impact of this challenge is to adhere to the second of the SOLID principles: the Open-Closed Principle (OCP).
One of the most important elements of a software engineer’s personal development is reading. In a field so vast, and so varied, constant reading is important both for building foundational knowledge and exploring branch knowledge. And as in any profession where the written word plays a large role, software has it’s 'must read' books. One of those, is Clean Code, by Robert C. Martin.
If you’ve been around software for a while, then you’ve almost certainly heard of the SOLID principles. In short, these are a set of principles intended to help developers write clean, well-structured, and easily-maintainable code. In software, as in any intellectual and creative endeavor, there is quite a bit of debate about the “right” way to do things. Different practitioners have different ideas about what is “right”, depending on their individual experiences and inclinations.
Tag: principles (p. 1)