{"id":13795,"date":"2015-06-08T11:00:00","date_gmt":"2015-06-08T15:00:00","guid":{"rendered":"https:\/\/simpleprogrammer.com\/?p=13795"},"modified":"2018-01-23T13:24:21","modified_gmt":"2018-01-23T18:24:21","slug":"design-patterns-simplified-the-bridge-pattern","status":"publish","type":"post","link":"https:\/\/simpleprogrammer.com\/design-patterns-simplified-the-bridge-pattern\/","title":{"rendered":"Bridge Pattern"},"content":{"rendered":"

Let me ask you a question?\\n\\nDo you really understand design patterns<\/strong>\u2014you know, the ones in that old Gang of Four book<\/a>?\\n\\nPerhaps you aren\u2019t even really familiar with the term \u201cdesign patterns.\u201d It\u2019s Ok, you are not alone. Design patterns are simply formal names given to common patterns that seem to emerge from solving various architectural problems in software development.\\n\\nThe term \u201cdesign pattern\u201d became popular after the book, by the same name<\/a> was published was back in 1994. This landmark book is now affectionately referred to as the \u201cGang of Four\u201d book, after the 4 authors who co-wrote the book: Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides.\\n\\nAs good as the book is, it does have one major short-coming. It\u2019s a bit difficult to understand.\\n\\n\"\"Perhaps though, you already understand design patterns, but do you really get them at a deep level? For the longest time in my career, I didn\u2019t. Sure, I understood the basics, and I knew what Singleton was, but I didn\u2019t really understand the how and why of most of the somewhat complicated design patterns.<\/strong>\\n\\nI finally decided that enough was enough and I was going to scour the internet and books to find some simple explanations and examples of the design patterns that weren\u2019t so easily explained.\\n\\nWell, after all that searching, guess what? I didn\u2019t find what I was looking for. I found plenty of explanations of design patterns, but none of them were very simple.<\/strong> I found plenty of examples of the various design patterns, but most of them were the same old tired examples that existed everywhere else.\\n\\nSo, I decided that I was going to go through all that information and come up with my own examples, over and over again until I really, deeply understood all of the design patterns. The process was long\u2014and somewhat boring\u2014but, I when I was finished I was able to confidently say that I finally really understood design patterns.<\/strong>\\n\\n(I also created quite a few Pluralsight videos explaining many of the design patterns, with some real code examples. You can find those here.)<\/a>\\n\\n<\/p>\n

Sharing the Knowledge<\/h2>\n

\\n\\nIn this series of articles, I\u2019m going to take my lessons learned from going through all of the design patterns in depth and I am going to do my very best job to assimilate all that information into what I hope will be the most clear and easily understandable explanation of each of the patterns<\/strong>, starting with the Bridge pattern.\\n\\nIn this article, I will follow this format:\\n\\n<\/p>\n