Tackling the I in SOLID
When you are writing code, are you doing it right? That is a question that worries a lot of people, and it should probably at least be something every developer thinks through. Design patterns are best practice concepts that we can implement into our code to make it better in some way. Think of them as guardrails that keep our code safe. In this video, we are going to look at the fourth entry in the famous SOLID principle. The I stands for Interface Segregation Principle. We are going to dive into what it means, how it should change our programming practices, and how far we should take it.
Resources mentioned in the video
Sign up for my mailing list here: https://iamtimcorey.com/general-sign-up (your email will be kept safe and you will not be spammed).
Initial Source Code from the video: ISPDemo_Start
Completed Source Code from the video: ISPDemo_End