{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Code to an Interface: Everything You Need to Know","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/1e10a805\"></iframe>","width":"100%","height":180,"duration":420,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/code-to-an-interface-everything-you-need-to-know.\nHow 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.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            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.\nThis story was written by: @oussamamater. Learn more about this writer by checking @oussamamater's about page,\n            and for more stories, please visit hackernoon.com.\n\"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\".","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}