SOLID principles and you

If design patterns are the engineering classes aimed at solving problems repeatedly found in the wilds of programming, then the SOLID principles are philosophy seminars. If SOLID is a new acronym for you, don’t worry – here’s a quick breakdown of what’s in store:

Single-responsibility principle	There should never be more than one reason for a class to change, every class should only have one responsibility!
Open-closed principle	In a perfect world, entities (classes, functions, modules) should be open to extension but closed to modification, meaning new behaviors are allowed if the source code isn’t tampered with. We’ve seen this first-hand with abstract classes and interfaces that allow concrete implementations to be switched out anytime without...