Common Errors in Interface Design - #SOLID - ISP

The Interface Segregation Principle (ISP) hides some very subtle nuances that can go unnoticed. However, these nuances when interpreting the ISP are extremely important as they will aid in the proper design of our interfaces and, therefore, our application. In this video, we will mainly see what the concept "interfaces belong to the clients that use them, not to the classes that implement them" is based on. We will also talk about the "structural coupling" of our interfaces. I recommend giving the explanation a chance. At the beginning of the video, I think I get a bit confused, and as the video progresses, I believe it becomes clearer what I want to convey.

Thanks to Armando Antón for the comment in the previous video that made me rethink how I understood the ISP :D ! Sorry for the delay in publishing this video. I had some issues with iMovie when uploading the video to YouTube :-/ There won't be a video next week. See you the following one (Thursday 21)!

Pay according to your needs

lite (only monthly)

19 €
per month
  • Access to a subset of courses to lay the foundation for maintainable, scalable, and testable code
  • Company invoice
Popular

standard

24,92 €
Save 121
Annual payment of 299
per month
  • Full course catalog
  • Design and architecture challenges
  • Highlighted solutions videos for challenges
  • Receive job offers verified by Codely
  • Company invoice

premium

41,58 €
Save 89
Annual payment of 499
per month
  • Everything above
  • More benefits coming soon

We won’t increase the price while your subscription is active