Skip to main content

Posts

Showing posts from July, 2020

SOLID: Dependency Inversion Principle

About 5 years ago, I wrote a series of short articles on the SOLID principles, shared by email to my colleagues as a weekly, Monday morning read. They were then archived for reference to our internal knowledge base. That's getting a revamp and re-platforming now, and given their age, I'm not sure these pieces will be making the cut. Given it's fairly timeless stuff, seems a shame for them to disappear into the virtual ether, so I'll save them for posterity here.The SOLID PrinciplesThe SOLID principles are a well established set of tenets intended to guide software design toward a maintainable solution. They are widely applicable and operate at a high level, so are well worth considering for almost any type of application we are looking to build, using any framework or language.For the full set of articles in the series, see:S is for Single Responsibility PrincipleO is for Open/Closed PrincipleL is for Liskov Substitution PrincipleI is for Interface Segregation Princ…

SOLID: Interface Segregation Principle

About 5 years ago, I wrote a series of short articles on the SOLID principles, shared by email to my colleagues as a weekly, Monday morning read. They were then archived for reference to our internal knowledge base. That's getting a revamp and re-platforming now, and given their age, I'm not sure these pieces will be making the cut. Given it's fairly timeless stuff, seems a shame for them to disappear into the virtual ether, so I'll save them for posterity here.The SOLID PrinciplesThe SOLID principles are a well established set of tenets intended to guide software design toward a maintainable solution. They are widely applicable and operate at a high level, so are well worth considering for almost any type of application we are looking to build, using any framework or language.For the full set of articles in the series, see:S is for Single Responsibility PrincipleO is for Open/Closed PrincipleL is for Liskov Substitution PrincipleI is for Interface Segregation Princ…

SOLID: Liskov Substitution Principle

About 5 years ago, I wrote a series of short articles on the SOLID principles, shared by email to my colleagues as a weekly, Monday morning read. They were then archived for reference to our internal knowledge base. That's getting a revamp and re-platforming now, and given their age, I'm not sure these pieces will be making the cut. Given it's fairly timeless stuff, seems a shame for them to disappear into the virtual ether, so I'll save them for posterity here.The SOLID PrinciplesThe SOLID principles are a well established set of tenets intended to guide software design toward a maintainable solution. They are widely applicable and operate at a high level, so are well worth considering for almost any type of application we are looking to build, using any framework or language.For the full set of articles in the series, see:S is for Single Responsibility PrincipleO is for Open/Closed PrincipleL is for Liskov Substitution PrincipleI is for Interface Segregation Princ…

SOLID: Open/Closed Principle

About 5 years ago, I wrote a series of short articles on the SOLID principles, shared by email to my colleagues as a weekly, Monday morning read. They were then archived for reference to our internal knowledge base. That's getting a revamp and re-platforming now, and given their age, I'm not sure these pieces will be making the cut. Given it's fairly timeless stuff, seems a shame for them to disappear into the virtual ether, so I'll save them for posterity here.The SOLID PrinciplesThe SOLID principles are a well established set of tenets intended to guide software design toward a maintainable solution. They are widely applicable and operate at a high level, so are well worth considering for almost any type of application we are looking to build, using any framework or language.For the full set of articles in the series, see:S is for Single Responsibility PrincipleO is for Open/Closed PrincipleL is for Liskov Substitution PrincipleI is for Interface Segregation Princ…

SOLID: Single Responsibility Principle

About 5 years ago, I wrote a series of short articles on the SOLID principles, shared by email to my colleagues as a weekly, Monday morning read. They were then archived for reference to our internal knowledge base. That's getting a revamp and re-platforming now, and given their age, I'm not sure these pieces will be making the cut. Given it's fairly timeless stuff, seems a shame for them to disappear into the virtual ether, so I'll save them for posterity here.The SOLID PrinciplesThe SOLID principles are a well established set of tenets intended to guide software design toward a maintainable solution. They are widely applicable and operate at a high level, so are well worth considering for almost any type of application we are looking to build, using any framework or language.For the full set of articles in the series, see:S is for Single Responsibility PrincipleO is for Open/Closed PrincipleL is for Liskov Substitution PrincipleI is for Interface Segregation Princ…