CoursesAI WorkshopCompaniesPricingBlogConfAiBotSign inSubscribe
  • Courses
  • AI Workshop
  • Companies
  • Pricing
  • Blog
  • ConfAiBot
Subscribe
  • Courses
  • Companies
  • Communities
  • Blog
  • Gift card
  • Help
  • Shop
  • ConfAiBot
  • Contact
  • Legal notice
  • General conditions
  • Privacy policy
  • Cookies policy

Interface Segregation Principle - #SOLID

31 December 2015 | screencasts

Today we will delve into what the Interface Segregation Principle (or ISP) is based on. This principle, like the ones we have already covered on CodelyTV such as the Single Responsibility Principle or the Dependency Inversion Principle, is part of the 5 SOLID principles. The SOLID principles, as we know, are that set of best practices that help us in the design of our object-oriented programs so that, in summary, our code is more easily maintainable :)

For this video, I based it on the example of ISP published by Tuts+.

Tags

Code SmellsIntermediateRefactoringSOLID
AnteriorCommon Errors in Interface Design - #SOLID - ISP
SiguienteMultiple Returns in a Function: Good or Bad? - #Refactoring

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
  • Receive job offers verified by Codely
  • Company invoice

premium

41,58 €
Save 89 €
Annual payment of 499 €
per month
  • All previous benefits
  • Early access to new courses
  • Discount on workshops

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