Skip to content

Instantly share code, notes, and snippets.

@rbirkby

rbirkby/SolidQuotes.md

Last active December 17, 2015 02:59
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rbirkby/5539953 to your computer and use it in GitHub Desktop.
Save rbirkby/5539953 to your computer and use it in GitHub Desktop.
Download ZIP
SOLID quotes
Raw
SolidQuotes.md

I quite agree that a dogmatic or religious application of the SOLID principles is neither realistic nor beneficial. If you had read through any of the articles and/or books I’ve written on these principles over the last 15 years, you’d have found that I don’t recommend the religious or dogmatic approach you blamed me for. In short, you jumped to a erroneous conclusion about me, and about the principles, because you weren’t familiar with the material.

Robert C. Martin
https://sites.google.com/site/unclebobconsultingllc/an-open-letter-to-joel-spolsky-and-jeff-atwood

An axis of change is an axis of change only if the changes occur. It is not wise to apply SRP - or any other principle, for that matter - if there is no symptom.

Robert C. Martin
Page 118, Agile Principles, Patterns and Practices in C#

Clearly, we want to limit the application of OCP to changes that are likely.

Robert C. Martin
Page 129, Agile Principles, Patterns and Practices in C#

Nor is it a good idea to apply rampant abstraction to every part of the application. Rather, it requires a dedication on the part of the developers to apply abstraction only to those parts of the program that exhibit frequent change. Resisting premature abstraction is as important as abstraction itself

Robert C. Martin
Page 132, Agile Principles, Patterns and Practices in C#

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment