CUPID—for joyful coding

What started as lighthearted iconoclasm, poking at the bear of SOLID, has developed into something more concrete and tangible. If I do not think the SOLID principles are useful these days, then what would I replace them with? Can any set of principles hold for all software? What do we even mean by principles?

Design SOLID

May 12 2022

 Breaking Dependencies: The SOLID Principles

SOLID is an abbreviation for five of the most important software design principles: - (S)ingle Responsibility Principle - (O)pen-Closed Principle - (L)iskov Substitution Principle - (I)nterface Segregation Principle - (D)ependency Inversion Principle For almost two decades, these principles have proven to be a valuable set of guidelines to cope with software dependencies. Although initially introduced as guidelines for object-oriented programming, they have become a universal set of guidelines that can be used equally well for procedural, functional or generic programming. In this talk I'll recap the SOLID principles and explain why they form such a valuable set of universal design guidelines. Also, I'll go into detail about several common misconceptions.


Oct 20 2021