SOLID Seems to be the Hardest Word
- 01 Feb 2017
Yesterday I gave a talk at the Wellington .NET User Group on the SOLID principles drawing on some of my own personal experience and biases over the years. The slides to this can be found in the presentations sections; however since the slides on their own are useless without context I plan to turn the presentation into a short series of blog posts.
I’ll be focusing more on the applicability of the SOLID principles rather than the strict definition and code impacts, including:
- Why I personally think these principles are still relevant more than a decade on from their initial formation
- I’ll look at each of the principles to examine how and why each can be applied to benefit you as a developer
- What are some common problems with the principles and how you might overcome them
- And most importantly scenarios where you can apply SOLID that go beyond pure development of code
It’s my intent to provide a useful mid-level introduction into the application of SOLID, which’ll serve as a springboard to you considering these principles as a permanent tool in your development toolkit. It’s not my in my plan, or even in my capability, to provide a comprehensive / definitive overview of these principles and their impacts - there’s plenty enough detail already out there on this subject.
Finally be aware that these posts will be my own personal opinion, drawing on experiences I’ve had over the course of my career.