SOLID is STUPID

Breaking It Down

Don’t get me wrong; you absolutely should be following the general ideas behind SOLID in object-oriented languages (for the most part). What I take issue with is how they are presented. Let’s take a quick refresher course.

Single Responsibility Principle

Open-Closed Principle

Liskov Substitution Principle

Interface Segregation (and the rest)

This is where this whole initialism really starts to fall apart. Our previous principle (Liskov Substitution), Interface Segregation Principle, and Dependency Inversion, are all essentially covering the same single idea:

Wrapping It Up

Again, I need to be clear that much of the ideas in SOLID (except Open-Closed), are great general rules to follow in most scenarios. What I take issue with is how they are packaged.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Stephen Collins

Stephen Collins

A life-long geek focused on quality software and general code craftsmanship.