<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>design patterns on Murali Krishna</title><link>https://nocapstories.com/tags/design-patterns/</link><description>Recent content in design patterns on Murali Krishna</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Thu, 17 Jun 2021 16:48:06 +0530</lastBuildDate><atom:link href="https://nocapstories.com/tags/design-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Composition Over Inheritance - Strategy Pattern</title><link>https://nocapstories.com/posts/2021/06/composition-over-inheritance-strategy-pattern/</link><pubDate>Thu, 17 Jun 2021 16:48:06 +0530</pubDate><guid>https://nocapstories.com/posts/2021/06/composition-over-inheritance-strategy-pattern/</guid><description>Note : This article tries to summarize the major debate of &amp;ldquo;Composition vs Inheritance&amp;rdquo; from various articles/books. I tried to keep the examples/scenarios as concise &amp;amp; close to the original content as possible to make sure this sticks in your brain while studying the actual book.
Introduction Knowing the OO Basics does not make you a good OO Designer. A good Object Oriented Designer makes sure the code is resusable, extensible and maintainable.</description></item></channel></rss>