Sub-Domains That Follow the Single Responsibility Principle
The Single Responsibility Principle applies even to identifying sub-domains.
SOLID
Open-Closed Principle by Example: Conclusion
This series clarifies the Open-Closed Principle with examples. This post recaps what we’ve learned
Open-Closed Principle by Example: Anti-Examples
This series clarifies the Open-Closed Principle with examples. This post describes some approaches that may look like the OCP, but don’t deliver the expected value.
Open-Closed Principle by Example: OCP as Architecture
This series clarifies the Open-Closed Principle (OCP) with examples. This post applies the OCP to the system level with architecture patterns like ports and adapters.
Open-Closed Principle by Example: Interchangable Implementations
This series clarifies the Open-Closed Principle with examples. This post will demonstrate the OCP through interchangable and composable dependencies.
Open-Closed Principle by Example: Callbacks & Handlers
This series clarifies the Open-Closed Principle with examples. This post will demonstrate how the OCP can be achieved through flexible behaviors like callbacks.
Open-Closed Principle by Example: Flexibility Through Data
This series clarifies the Open-Closed Principle with examples. This post will demonstrate how the OCP can be achieved through flexible data.
Open-Closed Principle by Example: Introduction to OCP
The Open-Closed Principle, one of the SOLID principles, is crucial to reusable code and insulated problem domains. This series will clarify the principle with examples.
Are principles SMART?
SMART is a set of criteria for setting effective goals. I recently saw a recommendation that architecture principles should be SMART, but I’m not convinced.
SOLID vs SPNC
I previously enumerated a set of properties that underlay self-documenting code. Is there really a need for another set of properties?