Deploying to gh-pages from @ 982dab6 🚀

Author: danieldelcore

index.html

@@ -1051,6 +1051,7 @@ <h3 id="memoization">Memoization</h3>
 <h1 id="design-patterns">Design Patterns</h1>
 <h2 id="decorator">Decorator</h2>
 <p><a href="https://addyosmani.com/resources/essentialjsdesignpatterns/book/#decoratorpatternjavascript">Decorator</a></p>
+<p><a href="https://www.scaler.com/topics/design-patterns/decorator-design-pattern/">https://www.scaler.com/topics/design-patterns/decorator-design-pattern/</a></p>
 <p>Decorators are a structural design pattern that aim to promote code re-use. Similar to Mixins, they can be considered another viable alternative to object sub-classing.</p>
 <p>Classically, Decorators offered the ability to add behaviour to existing classes in a system dynamically. The idea was that the <em>decoration</em> itself wasn&#39;t essential to the base functionality of the class, otherwise it would be baked into the <em>superclass</em> itself.</p>
 <p>They can be used to modify existing systems where we wish to add additional features to objects without the need to heavily modify the underlying code using them. A common reason why developers use them is their applications may contain features requiring a large quantity of distinct types of object. Imagine having to define hundreds of different object constructors for say, a JavaScript game.</p>