Remove stark warning against duplicate code, let's just strongly suggest to avoid it

Author: ryanmcdermott

README.md

@@ -362,13 +362,26 @@ function parseBetterJSAlternative(code) {
 **[⬆ back to top](#table-of-contents)**
 
 ### Remove duplicate code
-Never ever, ever, under any circumstance, have duplicate code. There's no reason
-for it and it's quite possibly the worst sin you can commit as a professional
-developer. Duplicate code means there's more than one place to alter something
-if you need to change some logic. JavaScript is untyped, so it makes having
-generic functions quite easy. Take advantage of that! Tools like
-[jsinspect](https://github.com/danielstjules/jsinspect) can help you find duplicate
-code eligible for refactoring.
+Do your absolute best to avoid duplicate code. Duplicate code is bad because it
+means that there's more than one place to alter something if you need to change
+some logic.
+
+Imagine if you run a restaurant and you keep track of your inventory: all your
+tomatoes, onions, garlic, spices, etc. If you have multiple lists that that
+you keep this on, then all have to be updated when you serve a dish with
+tomatoes in them. If you only have one list, there's only one place to update!
+
+Oftentimes you have duplicate code because you have two or more slightly
+different things, that share a lot in common, but their differences force you
+to have two or more separate functions that do much of the same things. Removing
+duplicate code means creating an abstraction that can handle this set of
+different things with just one function/module/class.
+
+Getting the abstraction right is critical, that's why you should follow the
+SOLID principles laid out in the *Classes* section. Bad abstractions can be
+worse than duplicate code, so be careful! Having said this, if you can make
+a good abstraction, do it! Don't repeat yourself, otherwise you'll find yourself
+updating multiple places anytime you want to change one thing.
 
 **Bad:**
 ```javascript