I like to regularly (re-)examine engineering theory and wisdom to see how it holds up today — both from the perspective of current trends and my own growing experience. I've scratched the surface of the SOLID principles many times, but regularly struggled to commit them to memory. This time, I'd like to write the reference to my own understanding of each.

SOLID?

SOLID is an acronym, with each letter describing a tenet which is believed to help design good object-oriented software. They were introduced by Robert C. Martin — also weirdly known as "Uncle Bob," but I'll call him "Bob" to meet in the middle of my dignity and his wishes — in Design Principles and Design Patterns. There's an archived copy available courtesy of the Wayback Machine in case you want to give it a read.

Why talk about SOLID?

There are hundreds of design principles, patterns, maxims, creeds, etc. out there, and I'd love to get into more of them. The SOLID set are almost universally known — or at least known of — so I feel like it's as good a place as any to start.

My intention is to dive reasonably deep into each piece of SOLID, with my own examples and opinions. Each will therefore live in its own article, which will be linked below as it is published.

Don't want to miss one? Consider subscribing!