Tag Archives: architect design principles

Learning The S.O.L.I.D Programming Principles: Dependency inversion principle [Part – VI]

History: In our previous posts we learned ‘What is S.O.L.I.D. Programing Principles’ and a detailed explalantion with code of Single Responsibility Principle, Open/closed Principle, Liskov Substitution Principle and Interface Segregation Principle. S.O.L.I.D. is an acronym introduced by Michael Feathers as: S for SRP: Single responsibility principle O for OCP: Open/closed principle L for LSP: Liskov

Read More

Learning The S.O.L.I.D Programming Principles: Interface segregation principle [Part – V]

History: In our previous posts we learned ‘What is S.O.L.I.D. Programing Principles’ and a detailed explalantion with code of Single Responsibility Principle, Open/closed Principle and Liskov Substitution Principle. S.O.L.I.D. is an acronym introduced by Michael Feathers as: S for SRP: Single responsibility principle O for OCP: Open/closed principle L for LSP: Liskov substitution principle I

Read More

Learning The S.O.L.I.D Programming Principles: Liskov substitution principle [Part – IV]

History: In our previous posts we learned ‘What is S.O.L.I.D. Programing Principles’ and a detailed explanation with code of Single Responsibility Principle and Open/closed Principle. S.O.L.I.D. is an acronym introduced by Michael Feathers as: S for SRP: Single responsibility principle O for OCP: Open/closed principle L for LSP: Liskov substitution principle I for ISP: Interface

Read More

Learning The S.O.L.I.D Programming Principles: Overview [Part – I]

Earlier, I was thinking that learning of Object Oriented Programings (OOPs) is enough to write robust, scalable and re-usable application/program. When I discussed the things with Joseph Bulger, I was shocked because I was thinking that my programming skills are within OOPs and learning of new languages like C/C++/C#/F# etc. So, I started learning “The

Read More