Previous post in this series:SOLID – SRP – Ignoring the rules on the paint can SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION. When a single change to a program results in a cascade of changes to dependent modules, that program exhibits the undesirable attributes that we have […]
. Read more
Previous post in this series:SOLID – (SRP) The Single Responsibility Principle Some of my source links in the previous two posts may not have worked in FireFox (but worked fine in IE and Chrome). These links have been fixed. It was an issue with how google was handling the redirects to the source files. In […]
. Read more
Previous post in this series:SOLID – Getting Started and Source Material Original Source Material on SRP I’m sure most of us have taken an Object Oriented Programming (OOP) class in college (or will soon). What is important to understand is that an OOP class will teach you the fundamentals of understanding the principles of developing […]
. Read more
This next series will follow the principles of SOLID, “five basic principles of object-oriented programming and design.” The concepts as collated into SOLID was organized by a gentleman named Robert C. Martin who has what may be one of my favorite quotes in software engineering: Following the rules on the paint can won’t teach you […]
. Read more