From e480290d38473d74b32ad49205d5c25501868fa1 Mon Sep 17 00:00:00 2001 From: FARHAN-72 <71866464+FARHAN-72@users.noreply.github.com> Date: Thu, 1 Oct 2020 13:53:18 +0530 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 603393e..d2eb7c2 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# JavaScript Design Patterns +# JavaScript Design Patterns [AMAZING DESIGN] ## Creational @@ -42,4 +42,4 @@ I know there are a lot of people out there who aren’t too keen on design patte Patterns should be used with caution as not everything fits so neatly into their paradigms. It’s often said that a beginner never met a pattern he didn’t like. In my experiences I’ve been burned by pattern overuse and at other times they have legitimately saved my ass. It’s also true that many patterns don’t really work or aren’t appropriate for particular languages. For instance, the GoF book was written primarily for languages which shared features of C++ and SmallTalk. I totally agree with this sentiment but I feel like along the way we’ll discover what does and doesn’t make sense in a dynamic language like JS and hopefully we can toss in some new patterns of our own. Already to the list I’ve added Promises which I use quite frequently and find to be a wonderful alternative to JavaScript’s oft seen pyramid of callbacks. Again, this is all about learning and experimenting. In my opinion a good understanding of design patterns is a threshold that needs to be crossed at some point in your career. I’m committed to doing this twice a week for the next several weeks so hopefully by the end of it we’ll have a useful resource that others can benefit from. Stay tuned! -[http://robdodson.me/blog/2012/08/03/javascript-design-patterns/](http://robdodson.me/blog/2012/08/03/javascript-design-patterns/) \ No newline at end of file +[http://robdodson.me/blog/2012/08/03/javascript-design-patterns/](http://robdodson.me/blog/2012/08/03/javascript-design-patterns/)