Pragmatic SOILD

The desired outcome of this series is to save you time and money. Knowing the benefits of the SOLID design principles will empower you to selectively produce more maintainable and less error prone software at the appropriate moment.

Each topic follows the same pattern; where the brief principle is stated, followed by a summary for those short of time (TL;DR – Too long didn’t read). Then, I state the business value and elaborate examples of applying the principle. I then provide an ego-filling ‘Middleton test’ which helps you decide if the time to apply the principle is right. I then finish with references or further examples.

The conclusion to the complete series is simple. Knowing SOLID sets a professional developer apart from the crowd, but applying SOLID prematurely, liberally or too enthusiastically can be just as detrimental as not knowing the principles at all.

S The Single Responsibility Principle

O The Open/Closed Principle

L The Liskov Substitution Principle

I The Interface Segregation Principle

D The Dependency Inversion Principle

Please do take the time to leave comments. I’m open to challenge and any improvements to these articles.

(C) Giles Middleton  2013

Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s