Code to an Interface: Everything You Need to Know

Programming Tech Brief By HackerNoon

HackerNoon에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 HackerNoon 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

약 1년 전 7:00

MP3•에피소드 홈

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".