If you follow good design principles and good dev practices and utilize the APIs and SDKS Microsoft has made available within the .NET Framework, you don’t need to know anything about patterns. There, I said it. You don’t need to know anything about patterns. Now why would I think this? Well, a few years ago […]
. Read more
Here is the list of all the posts in my series on SOLID. SOLID – Getting Started and Source MaterialSOLID – (SRP) The Single Responsibility PrincipleSOLID – (SRP) Ignoring the rules on the paint canSOLID – (OCP) The Open-Closed PrincipleSOLID – (LSP) The Liskov Substitution PrincipleSOLID – (ISP) The Interface Segregation PrincipleSOLID – (DIP) The […]
. Read more
Previous post in this series:SOLID – (ISP) The Interface Segregation Principle A. HIGH LEVEL MODULES SHOULD NOT DEPEND UPON LOW LEVEL MODULES. BOTH SHOULD DEPEND UPON ABSTRACTIONS B. ABSTRACTIONS SHOULD NOT DEPEND UPON DETAILS. DETAILS SHOULD DEPEND UPON ABSTRACTIONS. The Dependency Inversion Principle, Robert C. Martin The DIP is part and parcel with the OCP […]
. Read more
Previous post in this series:SOLID – (LSP) The Liskov Substitution Principle CLIENTS SHOULD NOT BE FORCED TO DEPEND UPON INTERFACES THAT THEY DO NOT USE. When clients are forced to depend upon interfaces that they don’t use, then those clients are subject to changes to those interfaces. This results in an inadvertent coupling between all […]
. Read more
Previous post in this series:SOLID – (OCP) The Open-Closed Principle FUNCTIONS THAT USE POINTERS OR REFERENCES TO BASE CLASSES MUST BE ABLE TO USE OBJECTS OF DERIVED CLASSES WITHOUT KNOWING IT. The importance of this principle becomes obvious when you consider the consequences of violating it. If there is a function which does not conform […]
. Read more