
Code to an Interface: Everything You Need to Know
About this episode
This story was originally published on HackerNoon at: https://hackernoon.com/code-to-an-interface-everything-you-need-to-know.
How often have you heard "Code to an interface"? I'm sure, at least a few times, and I know it can be hard to understand at first. So let's see what it means.
Check more stories related to programming at: https://hackernoon.com/c/programming.
You can also check exclusive content about #solid-principles, #software-architecture, #php, #code-to-an-interface, #coding-tutorial, #open-closed-principle, #liskov-substitution-principle, #hackernoon-top-story, and more.
This story was written by: @oussamamater. Learn more about this writer by checking @oussamamater's about page,
and for more stories, please visit hackernoon.com.
"Code to an interface" never made sense to me. I questioned the need to create an interface and then implement it. How do I determine when and where to use these interfaces? If you're experiencing this, know that we've all been there. Let's help you understand why you need to "Code to interface".
Get every episode summarized
Each time Programming Tech Brief By HackerNoon publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Programming Tech Brief By HackerNoon

Build a Tiny Grep Clone While Rust Teaches You Who Owns What
Programming Tech Brief By HackerNoon

Deterministic Routing: The Hidden Key to Low Latency
Programming Tech Brief By HackerNoon

The Classic Computer Vision Trick Behind Smooth Image Blending
Programming Tech Brief By HackerNoon

7 Essential IP Geolocation API Features Every Developer Needs
Programming Tech Brief By HackerNoon