Programming To An Interface overview
This page collects available information about Programming To An Interface and organizes it in an easy-to-read reference format.
Key information
How to follow the principle of Couple To Abstractions, Not Concretions, and how to avoid tempting others to break the rule.
You've probably seen it: IOrderService, IEmailService, IPaymentService and every class has exactly one implementation.
You're not a soothsayer, so don't try to predict the future use cases of your code! Writing functions with an
Video Content: ---------------------------------- 0:00 - Intro 1:12 - Pseudocode Problem 2:39 - Inheritance Solution 4:21 -
OFF ANY Springboard Tech Bootcamps with my code ALEXLEE1500. See if you qualify for the JOB GUARANTEE!
Context and analysis
Information related to Programming To An Interface can change over time. Compare new developments with public records and specialist sources.
Frequently asked questions
What information does this page include?
It includes a summary, related details, context, and links to material connected with Programming To An Interface.
Is the information updated?
The page is generated dynamically and can incorporate newer information as its available sources are refreshed.
Consult original sources when you need to confirm an important detail.
