Design Patterns: Interface Segregation Principle Explained Practically in C# (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. Newsletter signup (with exclusive discounts): https://signup.iamtimcorey.com/ (your email will be kept safe and you will not be spammed). Source Code: https://leadmagnets.app/?Resource=IInSOLID Blog: https://www.iamtimcorey.com/blog/36001/solid-in-csharp 0:00 - Intro 1:49 - Demo Code overview 2:55 - Interface Segregation Principle: ISP Explained 7:45 - Implementing ISP: Refactoring demo code 24:52 - Note on empty Interfaces 29:06 - Recap 30:14 - Organizing code base and note on namespaces 34:47 - Summary and concluding remarks