In the final part of the SOLID series, we discuss dependency organization and how to avoid changes that cascade throughout a program with the Dependency Inversion Principle.

• principles
• software
• solid

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.

• principles
• software
• solid

Decreasing coupling with the principle of least knowledge.

• design
• principles
• reference
• software

Guidelines for the effective partitioning of a software product's codebase.

• principles
• reference
• software

The relationship between 'injecting' and 'inverting' dependencies in object-oriented design.

• design
• principles
• reference
• software

In part 3 of the SOLID series, we discuss the Liskov Substitution Principle (LSP) and how you can use it to ensure that a given object and all of its subtypes can be used interchangeably.

• principles
• software
• solid

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).

• principles
• software
• solid

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.

• books
• principles
• software
• solid

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.

• principles
• software
• solid