Uploaded October 2021 | Updated September 2026, 2 weeks ago

---

When your client code implements methods it doesn’t use, you have a problem. You’re violating the Interface Segregation Principle.

Your code will be coupled and more difficult to maintain.

In this video, you can learn about the Interface Segregation Principle, how to spot its violations, and how you can refactor ML code to respect it.

By adhering to ISP, your ML code will be cleaner and more maintainable in the longer run.

This video is part of the “Uncle Bob’s #SOLID principles for ML engineers” series.

Slides:
github.com/musikalkemist/solidforml/tree/main/solidforml/05%20Interface%20Segregation%20Principle

Code:
github.com/musikalkemist/solidforml/tree/main/solidforml/05%20Interface%20Segregation%20Principle

===============================

Interested in hiring me as a consultant/freelancer?
valeriovelardo.com

Join The Sound Of AI Slack community:
valeriovelardo.com/the-sound-of-ai-community

Connect with Valerio on Linkedin:
linkedin.com/in/valeriovelardo

Follow Valerio on Facebook:
facebook.com/TheSoundOfAI

Follow Valerio on Twitter:
twitter.com/musikalkemist​

===============================

Content:
0:00 Intro
0:16 Defining Interface Segretation Principle
0:37 ISP: The intruition
1:29 Spotting ISP violations
2:08 ISP violation problems
2:36 The Python example: Recommendation
6:44 Class diagram and ISP violation in example
7:09 Solving ISP violation: The idea
8:34 Solving ISP with hierarchical interfaces
9:47 Solving ISP with multiple inheritance
12:43 What's next?