Rock Solid -

    Rocking SOLID should be a top priority for any team coding in OOP. SOLID is a group of design principles which offer guidance to developers designing and coding complex applications. But, before I begin I have to rant. Professionals in any field love to create complex jargon through legalese, academese, and other species of “intellectual” and pretentious vernacular. Maybe it helps them feel big, special, smart, or part of a clique. Who knows. Whatever the reason, it’s crippling to those learning and damaging to those trying to communicate with others. Einstein said it best, “If you can’t explain it simply, you don’t understand it well enough.”

    SOLID may be intimidating the first time you come across it; the principle names ring of scientific conceit but don’t let this keep you from learning. Over the next 5 posts, let’s get together and break down each principle. We’ll look at how teams adopting SOLID have given rise to clean, concise, and maintainable code.

Part 1: SRP – Single Responsibility Principle

Part  2: OCP – Open/Closed Principle

Part 3: LSP –  Liskov Substitution Principle

Part 4: ISP – Interface Segregation Principle

Part 5: DSP – Dependency Inversion Principle


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