Add proper introduction

ryanmcdermott · ryanmcdermott · commit 85bfa0c4776a · 2017-01-02T14:43:33.000-08:00
diff --git a/README.md b/README.md
@@ -1,10 +1,7 @@
 # clean-code-javascript
-Software engineering principles, from Robert C. Martin's book
-[*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882),
-adapted for JavaScript. This is not a style guide. It's a guide to producing
-readable, reusable, and refactorable software in JavaScript. Enjoy!
 
 ## Table of Contents
+  0. [Introduction](#introduction)
   1. [Variables](#variables)
   2. [Functions](#functions)
   3. [Objects and Data Structures](#objects-and-data-structures)
@@ -14,6 +11,33 @@ readable, reusable, and refactorable software in JavaScript. Enjoy!
   7. [Formatting](#formatting)
   8. [Comments](#comments)
 
+## Introduction
+![Humorous image of software quality estimation as a count of how many expletives
+you shout when reading code](http://www.osnews.com/images/comics/wtfm.jpg)
+
+Software engineering principles, from Robert C. Martin's book
+[*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882),
+adapted for JavaScript. This is not a style guide. It's a guide to producing
+readable, reusable, and refactorable software in JavaScript.
+
+Not every principle herein has to be strictly followed, and even less will be
+universally agreed upon. These are guidelines and nothing more, but they are
+ones codified over many years of collective experience by the authors of
+*Clean Code*.
+
+Our craft of software engineering is just a bit over 50 years old, and we are
+still learning a lot. When software architecture is as old as architecture
+itself, maybe then we will have harder rules to follow. For now, let these
+guidelines serve as a touchstone by which to assess the quality of the
+JavaScript code that you and your team produce.
+
+One more thing: knowing these won't immediately make you a better software
+developer, and working with them for many years doesn't mean you won't make
+mistakes. Every piece of code starts as a first draft, like wet clay getting
+shaped into its final form. Finally, we chisel away the imperfections when
+we review it with our peers. Don't beat yourself up for first drafts that need
+improvement. Beat up the code instead!
+
 ## **Variables**
 ### Use meaningful and pronounceable variable names
 
