From 1d0c77847b7e5715d7db7552833f8d53c38663a3 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Tue, 17 Jan 2017 07:02:33 +0800
Subject: [PATCH 01/54] copy to zh-CN , start translation.

---
 README-zh-CN.md | 2106 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 2106 insertions(+)
 create mode 100644 README-zh-CN.md

diff --git a/README-zh-CN.md b/README-zh-CN.md
new file mode 100644
index 00000000..c612ec5a
--- /dev/null
+++ b/README-zh-CN.md
@@ -0,0 +1,2106 @@
+# clean-code-javascript
+
+## Table of Contents
+  1. [Introduction](#introduction)
+  2. [Variables](#variables)
+  3. [Functions](#functions)
+  4. [Objects and Data Structures](#objects-and-data-structures)
+  5. [Classes](#classes)
+  6. [Testing](#testing)
+  7. [Concurrency](#concurrency)
+  8. [Error Handling](#error-handling)
+  9. [Formatting](#formatting)
+  10. [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 fewer 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
+
+**Bad:**
+```javascript
+const yyyymmdstr = moment().format('YYYY/MM/DD');
+```
+
+**Good**:
+```javascript
+const currentDate = moment().format('YYYY/MM/DD');
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Use the same vocabulary for the same type of variable
+
+**Bad:**
+```javascript
+getUserInfo();
+getClientData();
+getCustomerRecord();
+```
+
+**Good**:
+```javascript
+getUser();
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Use searchable names
+We will read more code than we will ever write. It's important that the code we
+do write is readable and searchable. By *not* naming variables that end up
+being meaningful for understanding our program, we hurt our readers.
+Make your names searchable. Tools like
+[buddy.js](https://github.com/danielstjules/buddy.js) and
+[ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
+can help identify unnamed constants.
+
+**Bad:**
+```javascript
+// What the heck is 86400000 for?
+setTimeout(blastOff, 86400000);
+
+```
+
+**Good**:
+```javascript
+// Declare them as capitalized `const` globals.
+const MILLISECONDS_IN_A_DAY = 86400000;
+
+setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Use explanatory variables
+**Bad:**
+```javascript
+const address = 'One Infinite Loop, Cupertino 95014';
+const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
+saveCityZipCode(address.match(cityZipCodeRegex)[1], address.match(cityZipCodeRegex)[2]);
+```
+
+**Good**:
+```javascript
+const address = 'One Infinite Loop, Cupertino 95014';
+const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
+const [, city, zipCode] = address.match(cityZipCodeRegex) || [];
+saveCityZipCode(city, zipCode);
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid Mental Mapping
+Explicit is better than implicit.
+
+**Bad:**
+```javascript
+const locations = ['Austin', 'New York', 'San Francisco'];
+locations.forEach((l) => {
+  doStuff();
+  doSomeOtherStuff();
+  // ...
+  // ...
+  // ...
+  // Wait, what is `l` for again?
+  dispatch(l);
+});
+```
+
+**Good**:
+```javascript
+const locations = ['Austin', 'New York', 'San Francisco'];
+locations.forEach((location) => {
+  doStuff();
+  doSomeOtherStuff();
+  // ...
+  // ...
+  // ...
+  dispatch(location);
+});
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Don't add unneeded context
+If your class/object name tells you something, don't repeat that in your
+variable name.
+
+**Bad:**
+```javascript
+const Car = {
+  carMake: 'Honda',
+  carModel: 'Accord',
+  carColor: 'Blue'
+};
+
+function paintCar(car) {
+  car.carColor = 'Red';
+}
+```
+
+**Good**:
+```javascript
+const Car = {
+  make: 'Honda',
+  model: 'Accord',
+  color: 'Blue'
+};
+
+function paintCar(car) {
+  car.color = 'Red';
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Use default arguments instead of short circuiting or conditionals
+
+**Bad:**
+```javascript
+function createMicrobrewery(name) {
+  const breweryName = name || 'Hipster Brew Co.';
+  // ...
+}
+
+```
+
+**Good**:
+```javascript
+function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
+  // ...
+}
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+## **Functions**
+### Function arguments (2 or fewer ideally)
+Limiting the amount of function parameters is incredibly important because it
+makes testing your function easier. Having more than three leads to a
+combinatorial explosion where you have to test tons of different cases with
+each separate argument.
+
+Zero arguments is the ideal case. One or two arguments is ok, and three should
+be avoided. Anything more than that should be consolidated. Usually, if you have
+more than two arguments then your function is trying to do too much. In cases
+where it's not, most of the time a higher-level object will suffice as an
+argument.
+
+Since JavaScript allows us to make objects on the fly, without a lot of class
+boilerplate, you can use an object if you are finding yourself needing a
+lot of arguments.
+
+**Bad:**
+```javascript
+function createMenu(title, body, buttonText, cancellable) {
+  // ...
+}
+```
+
+**Good**:
+```javascript
+const menuConfig = {
+  title: 'Foo',
+  body: 'Bar',
+  buttonText: 'Baz',
+  cancellable: true
+};
+
+function createMenu(config) {
+  // ...
+}
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Functions should do one thing
+This is by far the most important rule in software engineering. When functions
+do more than one thing, they are harder to compose, test, and reason about.
+When you can isolate a function to just one action, they can be refactored
+easily and your code will read much cleaner. If you take nothing else away from
+this guide other than this, you'll be ahead of many developers.
+
+**Bad:**
+```javascript
+function emailClients(clients) {
+  clients.forEach((client) => {
+    const clientRecord = database.lookup(client);
+    if (clientRecord.isActive()) {
+      email(client);
+    }
+  });
+}
+```
+
+**Good**:
+```javascript
+function emailClients(clients) {
+  clients
+    .filter(isClientActive)
+    .forEach(email);
+}
+
+function isClientActive(client) {
+  const clientRecord = database.lookup(client);
+  return clientRecord.isActive();
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Function names should say what they do
+
+**Bad:**
+```javascript
+function addToDate(date, month) {
+  // ...
+}
+
+const date = new Date();
+
+// It's hard to to tell from the function name what is added
+addToDate(date, 1);
+```
+
+**Good**:
+```javascript
+function addMonthToDate(month, date) {
+  // ...
+}
+
+const date = new Date();
+addMonthToDate(1, date);
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Functions should only be one level of abstraction
+When you have more than one level of abstraction your function is usually
+doing too much. Splitting up functions leads to reusability and easier
+testing.
+
+**Bad:**
+```javascript
+function parseBetterJSAlternative(code) {
+  const REGEXES = [
+    // ...
+  ];
+
+  const statements = code.split(' ');
+  const tokens = [];
+  REGEXES.forEach((REGEX) => {
+    statements.forEach((statement) => {
+      // ...
+    });
+  });
+
+  const ast = [];
+  tokens.forEach((token) => {
+    // lex...
+  });
+
+  ast.forEach((node) => {
+    // parse...
+  });
+}
+```
+
+**Good**:
+```javascript
+function tokenize(code) {
+  const REGEXES = [
+    // ...
+  ];
+
+  const statements = code.split(' ');
+  const tokens = [];
+  REGEXES.forEach((REGEX) => {
+    statements.forEach((statement) => {
+      tokens.push( /* ... */ );
+    });
+  });
+
+  return tokens;
+}
+
+function lexer(tokens) {
+  const ast = [];
+  tokens.forEach((token) => {
+    ast.push( /* ... */ );
+  });
+
+  return ast;
+}
+
+function parseBetterJSAlternative(code) {
+  const tokens = tokenize(code);
+  const ast = lexer(tokens);
+  ast.forEach((node) => {
+    // parse...
+  });
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Remove duplicate code
+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
+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
+function showDeveloperList(developers) {
+  developers.forEach((developer) => {
+    const expectedSalary = developer.calculateExpectedSalary();
+    const experience = developer.getExperience();
+    const githubLink = developer.getGithubLink();
+    const data = {
+      expectedSalary,
+      experience,
+      githubLink
+    };
+
+    render(data);
+  });
+}
+
+function showManagerList(managers) {
+  managers.forEach((manager) => {
+    const expectedSalary = manager.calculateExpectedSalary();
+    const experience = manager.getExperience();
+    const portfolio = manager.getMBAProjects();
+    const data = {
+      expectedSalary,
+      experience,
+      portfolio
+    };
+
+    render(data);
+  });
+}
+```
+
+**Good**:
+```javascript
+function showList(employees) {
+  employees.forEach((employee) => {
+    const expectedSalary = employee.calculateExpectedSalary();
+    const experience = employee.getExperience();
+
+    let portfolio = employee.getGithubLink();
+
+    if (employee.type === 'manager') {
+      portfolio = employee.getMBAProjects();
+    }
+
+    const data = {
+      expectedSalary,
+      experience,
+      portfolio
+    };
+
+    render(data);
+  });
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Set default objects with Object.assign
+
+**Bad:**
+```javascript
+const menuConfig = {
+  title: null,
+  body: 'Bar',
+  buttonText: null,
+  cancellable: true
+};
+
+function createMenu(config) {
+  config.title = config.title || 'Foo';
+  config.body = config.body || 'Bar';
+  config.buttonText = config.buttonText || 'Baz';
+  config.cancellable = config.cancellable === undefined ? config.cancellable : true;
+}
+
+createMenu(menuConfig);
+```
+
+**Good**:
+```javascript
+const menuConfig = {
+  title: 'Order',
+  // User did not include 'body' key
+  buttonText: 'Send',
+  cancellable: true
+};
+
+function createMenu(config) {
+  config = Object.assign({
+    title: 'Foo',
+    body: 'Bar',
+    buttonText: 'Baz',
+    cancellable: true
+  }, config);
+
+  // config now equals: {title: "Order", body: "Bar", buttonText: "Send", cancellable: true}
+  // ...
+}
+
+createMenu(menuConfig);
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Don't use flags as function parameters
+Flags tell your user that this function does more than one thing. Functions should do one thing. Split out your functions if they are following different code paths based on a boolean.
+
+**Bad:**
+```javascript
+function createFile(name, temp) {
+  if (temp) {
+    fs.create(`./temp/${name}`);
+  } else {
+    fs.create(name);
+  }
+}
+```
+
+**Good**:
+```javascript
+function createFile(name) {
+  fs.create(name);
+}
+
+function createTempFile(name) {
+  createFile(`./temp/${name}`);
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid Side Effects
+A function produces a side effect if it does anything other than take a value in
+and return another value or values. A side effect could be writing to a file,
+modifying some global variable, or accidentally wiring all your money to a
+stranger.
+
+Now, you do need to have side effects in a program on occasion. Like the previous
+example, you might need to write to a file. What you want to do is to
+centralize where you are doing this. Don't have several functions and classes
+that write to a particular file. Have one service that does it. One and only one.
+
+The main point is to avoid common pitfalls like sharing state between objects
+without any structure, using mutable data types that can be written to by anything,
+and not centralizing where your side effects occur. If you can do this, you will
+be happier than the vast majority of other programmers.
+
+**Bad:**
+```javascript
+// Global variable referenced by following function.
+// If we had another function that used this name, now it'd be an array and it could break it.
+let name = 'Ryan McDermott';
+
+function splitIntoFirstAndLastName() {
+  name = name.split(' ');
+}
+
+splitIntoFirstAndLastName();
+
+console.log(name); // ['Ryan', 'McDermott'];
+```
+
+**Good**:
+```javascript
+function splitIntoFirstAndLastName(name) {
+  return name.split(' ');
+}
+
+const name = 'Ryan McDermott';
+const newName = splitIntoFirstAndLastName(name);
+
+console.log(name); // 'Ryan McDermott';
+console.log(newName); // ['Ryan', 'McDermott'];
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Don't write to global functions
+Polluting globals is a bad practice in JavaScript because you could clash with another
+library and the user of your API would be none-the-wiser until they get an
+exception in production. Let's think about an example: what if you wanted to
+extend JavaScript's native Array method to have a `diff` method that could
+show the difference between two arrays? You could write your new function
+to the `Array.prototype`, but it could clash with another library that tried
+to do the same thing. What if that other library was just using `diff` to find
+the difference between the first and last elements of an array? This is why it
+would be much better to just use ES2015/ES6 classes and simply extend the `Array` global.
+
+**Bad:**
+```javascript
+Array.prototype.diff = function diff(comparisonArray) {
+  const hash = new Set(comparisonArray);
+  return this.filter(elem => !hash.has(elem));
+};
+```
+
+**Good:**
+```javascript
+class SuperArray extends Array {
+  diff(comparisonArray) {
+    const hash = new Set(comparisonArray);
+    return this.filter(elem => !hash.has(elem));
+  }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Favor functional programming over imperative programming
+JavaScript isn't a functional language in the way that Haskell is, but it has
+a functional flavor to it. Functional languages are cleaner and easier to test.
+Favor this style of programming when you can.
+
+**Bad:**
+```javascript
+const programmerOutput = [
+  {
+    name: 'Uncle Bobby',
+    linesOfCode: 500
+  }, {
+    name: 'Suzie Q',
+    linesOfCode: 1500
+  }, {
+    name: 'Jimmy Gosling',
+    linesOfCode: 150
+  }, {
+    name: 'Gracie Hopper',
+    linesOfCode: 1000
+  }
+];
+
+let totalOutput = 0;
+
+for (let i = 0; i < programmerOutput.length; i++) {
+  totalOutput += programmerOutput[i].linesOfCode;
+}
+```
+
+**Good**:
+```javascript
+const programmerOutput = [
+  {
+    name: 'Uncle Bobby',
+    linesOfCode: 500
+  }, {
+    name: 'Suzie Q',
+    linesOfCode: 1500
+  }, {
+    name: 'Jimmy Gosling',
+    linesOfCode: 150
+  }, {
+    name: 'Gracie Hopper',
+    linesOfCode: 1000
+  }
+];
+
+const totalOutput = programmerOutput
+  .map((programmer) => programmer.linesOfCode)
+  .reduce((acc, linesOfCode) => acc + linesOfCode, 0);
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Encapsulate conditionals
+
+**Bad:**
+```javascript
+if (fsm.state === 'fetching' && isEmpty(listNode)) {
+  // ...
+}
+```
+
+**Good**:
+```javascript
+function shouldShowSpinner(fsm, listNode) {
+  return fsm.state === 'fetching' && isEmpty(listNode);
+}
+
+if (shouldShowSpinner(fsmInstance, listNodeInstance)) {
+  // ...
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid negative conditionals
+
+**Bad:**
+```javascript
+function isDOMNodeNotPresent(node) {
+  // ...
+}
+
+if (!isDOMNodeNotPresent(node)) {
+  // ...
+}
+```
+
+**Good**:
+```javascript
+function isDOMNodePresent(node) {
+  // ...
+}
+
+if (isDOMNodePresent(node)) {
+  // ...
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid conditionals
+This seems like an impossible task. Upon first hearing this, most people say,
+"how am I supposed to do anything without an `if` statement?" The answer is that
+you can use polymorphism to achieve the same task in many cases. The second
+question is usually, "well that's great but why would I want to do that?" The
+answer is a previous clean code concept we learned: a function should only do
+one thing. When you have classes and functions that have `if` statements, you
+are telling your user that your function does more than one thing. Remember,
+just do one thing.
+
+**Bad:**
+```javascript
+class Airplane {
+  // ...
+  getCruisingAltitude() {
+    switch (this.type) {
+      case '777':
+        return this.getMaxAltitude() - this.getPassengerCount();
+      case 'Air Force One':
+        return this.getMaxAltitude();
+      case 'Cessna':
+        return this.getMaxAltitude() - this.getFuelExpenditure();
+    }
+  }
+}
+```
+
+**Good**:
+```javascript
+class Airplane {
+  // ...
+}
+
+class Boeing777 extends Airplane {
+  // ...
+  getCruisingAltitude() {
+    return this.getMaxAltitude() - this.getPassengerCount();
+  }
+}
+
+class AirForceOne extends Airplane {
+  // ...
+  getCruisingAltitude() {
+    return this.getMaxAltitude();
+  }
+}
+
+class Cessna extends Airplane {
+  // ...
+  getCruisingAltitude() {
+    return this.getMaxAltitude() - this.getFuelExpenditure();
+  }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid type-checking (part 1)
+JavaScript is untyped, which means your functions can take any type of argument.
+Sometimes you are bitten by this freedom and it becomes tempting to do
+type-checking in your functions. There are many ways to avoid having to do this.
+The first thing to consider is consistent APIs.
+
+**Bad:**
+```javascript
+function travelToTexas(vehicle) {
+  if (vehicle instanceof Bicycle) {
+    vehicle.peddle(this.currentLocation, new Location('texas'));
+  } else if (vehicle instanceof Car) {
+    vehicle.drive(this.currentLocation, new Location('texas'));
+  }
+}
+```
+
+**Good**:
+```javascript
+function travelToTexas(vehicle) {
+  vehicle.move(this.currentLocation, new Location('texas'));
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid type-checking (part 2)
+If you are working with basic primitive values like strings, integers, and arrays,
+and you can't use polymorphism but you still feel the need to type-check,
+you should consider using TypeScript. It is an excellent alternative to normal
+JavaScript, as it provides you with static typing on top of standard JavaScript
+syntax. The problem with manually type-checking normal JavaScript is that
+doing it well requires so much extra verbiage that the faux "type-safety" you get
+doesn't make up for the lost readability. Keep your JavaScript clean, write
+good tests, and have good code reviews. Otherwise, do all of that but with
+TypeScript (which, like I said, is a great alternative!).
+
+**Bad:**
+```javascript
+function combine(val1, val2) {
+  if (typeof val1 === 'number' && typeof val2 === 'number' ||
+      typeof val1 === 'string' && typeof val2 === 'string') {
+    return val1 + val2;
+  }
+
+  throw new Error('Must be of type String or Number');
+}
+```
+
+**Good**:
+```javascript
+function combine(val1, val2) {
+  return val1 + val2;
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Don't over-optimize
+Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
+times, if you are optimizing then you are just wasting your time. [There are good
+resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)
+for seeing where optimization is lacking. Target those in the meantime, until
+they are fixed if they can be.
+
+**Bad:**
+```javascript
+
+// On old browsers, each iteration with uncached `list.length` would be costly
+// because of `list.length` recomputation. In modern browsers, this is optimized.
+for (let i = 0, len = list.length; i < len; i++) {
+  // ...
+}
+```
+
+**Good**:
+```javascript
+for (let i = 0; i < list.length; i++) {
+  // ...
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Remove dead code
+Dead code is just as bad as duplicate code. There's no reason to keep it in
+your codebase. If it's not being called, get rid of it! It will still be safe
+in your version history if you still need it.
+
+**Bad:**
+```javascript
+function oldRequestModule(url) {
+  // ...
+}
+
+function newRequestModule(url) {
+  // ...
+}
+
+const req = newRequestModule;
+inventoryTracker('apples', req, 'www.inventory-awesome.io');
+
+```
+
+**Good**:
+```javascript
+function newRequestModule(url) {
+  // ...
+}
+
+const req = newRequestModule;
+inventoryTracker('apples', req, 'www.inventory-awesome.io');
+```
+**[⬆ back to top](#table-of-contents)**
+
+## **Objects and Data Structures**
+### Use getters and setters
+JavaScript doesn't have interfaces or types so it is very hard to enforce this
+pattern, because we don't have keywords like `public` and `private`. As it is,
+using getters and setters to access data on objects is far better than simply
+looking for a property on an object. "Why?" you might ask. Well, here's an
+unorganized list of reasons why:
+
+* When you want to do more beyond getting an object property, you don't have
+to look up and change every accessor in your codebase.
+* Makes adding validation simple when doing a `set`.
+* Encapsulates the internal representation.
+* Easy to add logging and error handling when getting and setting.
+* Inheriting this class, you can override default functionality.
+* You can lazy load your object's properties, let's say getting it from a
+server.
+
+
+**Bad:**
+```javascript
+class BankAccount {
+  constructor() {
+    this.balance = 1000;
+  }
+}
+
+const bankAccount = new BankAccount();
+
+// Buy shoes...
+bankAccount.balance -= 100;
+```
+
+**Good**:
+```javascript
+class BankAccount {
+  constructor(balance = 1000) {
+    this._balance = balance;
+  }
+
+  // It doesn't have to be prefixed with `get` or `set` to be a getter/setter
+  set balance(amount) {
+    if (verifyIfAmountCanBeSetted(amount)) {
+      this._balance = amount;
+    }
+  }
+
+  get balance() {
+    return this._balance;
+  }
+
+  verifyIfAmountCanBeSetted(val) {
+    // ...
+  }
+}
+
+const bankAccount = new BankAccount();
+
+// Buy shoes...
+bankAccount.balance -= shoesPrice;
+
+// Get balance
+let balance = bankAccount.balance;
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Make objects have private members
+This can be accomplished through closures (for ES5 and below).
+
+**Bad:**
+```javascript
+
+const Employee = function(name) {
+  this.name = name;
+};
+
+Employee.prototype.getName = function getName() {
+  return this.name;
+};
+
+const employee = new Employee('John Doe');
+console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
+delete employee.name;
+console.log(`Employee name: ${employee.getName()}`); // Employee name: undefined
+```
+
+**Good**:
+```javascript
+const Employee = function (name) {
+  this.getName = function getName() {
+    return name;
+  };
+};
+
+const employee = new Employee('John Doe');
+console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
+delete employee.name;
+console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+## **Classes**
+### Single Responsibility Principle (SRP)
+As stated in Clean Code, "There should never be more than one reason for a class
+to change". It's tempting to jam-pack a class with a lot of functionality, like
+when you can only take one suitcase on your flight. The issue with this is
+that your class won't be conceptually cohesive and it will give it many reasons
+to change. Minimizing the amount of times you need to change a class is important.
+It's important because if too much functionality is in one class and you modify a piece of it,
+it can be difficult to understand how that will affect other dependent modules in
+your codebase.
+
+**Bad:**
+```javascript
+class UserSettings {
+  constructor(user) {
+    this.user = user;
+  }
+
+  changeSettings(settings) {
+    if (this.verifyCredentials()) {
+      // ...
+    }
+  }
+
+  verifyCredentials() {
+    // ...
+  }
+}
+```
+
+**Good**:
+```javascript
+class UserAuth {
+  constructor(user) {
+    this.user = user;
+  }
+
+  verifyCredentials() {
+    // ...
+  }
+}
+
+
+class UserSettings {
+  constructor(user) {
+    this.user = user;
+    this.auth = new UserAuth(user);
+  }
+
+  changeSettings(settings) {
+    if (this.auth.verifyCredentials()) {
+      // ...
+    }
+  }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Open/Closed Principle (OCP)
+As stated by Bertrand Meyer, "software entities (classes, modules, functions,
+etc.) should be open for extension, but closed for modification." What does that
+mean though? This principle basically states that you should allow users to
+add new functionalities without changing existing code.
+
+**Bad:**
+```javascript
+class AjaxAdapter extends Adapter {
+  constructor() {
+    super();
+    this.name = 'ajaxAdapter';
+  }
+}
+
+class NodeAdapter extends Adapter {
+  constructor() {
+    super();
+    this.name = 'nodeAdapter';
+  }
+}
+
+class HttpRequester {
+  constructor(adapter) {
+    this.adapter = adapter;
+  }
+
+  fetch(url) {
+    if (this.adapter.name === 'ajaxAdapter') {
+      return makeAjaxCall(url).then((response) => {
+        // transform response and return
+      });
+    } else if (this.adapter.name === 'httpNodeAdapter') {
+      return makeHttpCall(url).then((response) => {
+        // transform response and return
+      });
+    }
+  }
+}
+
+function makeAjaxCall(url) {
+  // request and return promise
+}
+
+function makeHttpCall(url) {
+  // request and return promise
+}
+```
+
+**Good**:
+```javascript
+class AjaxAdapter extends Adapter {
+  constructor() {
+    super();
+    this.name = 'ajaxAdapter';
+  }
+
+  request(url) {
+    // request and return promise
+  }
+}
+
+class NodeAdapter extends Adapter {
+  constructor() {
+    super();
+    this.name = 'nodeAdapter';
+  }
+
+  request(url) {
+    // request and return promise
+  }
+}
+
+class HttpRequester {
+  constructor(adapter) {
+    this.adapter = adapter;
+  }
+
+  fetch(url) {
+    return this.adapter.request(url).then((response) => {
+      // transform response and return
+    });
+  }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Liskov Substitution Principle (LSP)
+This is a scary term for a very simple concept. It's formally defined as "If S
+is a subtype of T, then objects of type T may be replaced with objects of type S
+(i.e., objects of type S may substitute objects of type T) without altering any
+of the desirable properties of that program (correctness, task performed,
+etc.)." That's an even scarier definition.
+
+The best explanation for this is if you have a parent class and a child class,
+then the base class and child class can be used interchangeably without getting
+incorrect results. This might still be confusing, so let's take a look at the
+classic Square-Rectangle example. Mathematically, a square is a rectangle, but
+if you model it using the "is-a" relationship via inheritance, you quickly
+get into trouble.
+
+**Bad:**
+```javascript
+class Rectangle {
+  constructor() {
+    this.width = 0;
+    this.height = 0;
+  }
+
+  setColor(color) {
+    // ...
+  }
+
+  render(area) {
+    // ...
+  }
+
+  setWidth(width) {
+    this.width = width;
+  }
+
+  setHeight(height) {
+    this.height = height;
+  }
+
+  getArea() {
+    return this.width * this.height;
+  }
+}
+
+class Square extends Rectangle {
+  setWidth(width) {
+    this.width = width;
+    this.height = width;
+  }
+
+  setHeight(height) {
+    this.width = height;
+    this.height = height;
+  }
+}
+
+function renderLargeRectangles(rectangles) {
+  rectangles.forEach((rectangle) => {
+    rectangle.setWidth(4);
+    rectangle.setHeight(5);
+    const area = rectangle.getArea(); // BAD: Will return 25 for Square. Should be 20.
+    rectangle.render(area);
+  });
+}
+
+const rectangles = [new Rectangle(), new Rectangle(), new Square()];
+renderLargeRectangles(rectangles);
+```
+
+**Good**:
+```javascript
+class Shape {
+  setColor(color) {
+    // ...
+  }
+
+  render(area) {
+    // ...
+  }
+}
+
+class Rectangle extends Shape {
+  constructor() {
+    super();
+    this.width = 0;
+    this.height = 0;
+  }
+
+  setWidth(width) {
+    this.width = width;
+  }
+
+  setHeight(height) {
+    this.height = height;
+  }
+
+  getArea() {
+    return this.width * this.height;
+  }
+}
+
+class Square extends Shape {
+  constructor() {
+    super();
+    this.length = 0;
+  }
+
+  setLength(length) {
+    this.length = length;
+  }
+
+  getArea() {
+    return this.length * this.length;
+  }
+}
+
+function renderLargeShapes(shapes) {
+  shapes.forEach((shape) => {
+    switch (shape.constructor.name) {
+      case 'Square':
+        shape.setLength(5);
+        break;
+      case 'Rectangle':
+        shape.setWidth(4);
+        shape.setHeight(5);
+    }
+
+    const area = shape.getArea();
+    shape.render(area);
+  });
+}
+
+const shapes = [new Rectangle(), new Rectangle(), new Square()];
+renderLargeShapes(shapes);
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Interface Segregation Principle (ISP)
+JavaScript doesn't have interfaces so this principle doesn't apply as strictly
+as others. However, it's important and relevant even with JavaScript's lack of
+type system.
+
+ISP states that "Clients should not be forced to depend upon interfaces that
+they do not use." Interfaces are implicit contracts in JavaScript because of
+duck typing.
+
+A good example to look at that demonstrates this principle in JavaScript is for
+classes that require large settings objects. Not requiring clients to setup
+huge amounts of options is beneficial, because most of the time they won't need
+all of the settings. Making them optional helps prevent having a "fat interface".
+
+**Bad:**
+```javascript
+class DOMTraverser {
+  constructor(settings) {
+    this.settings = settings;
+    this.setup();
+  }
+
+  setup() {
+    this.rootNode = this.settings.rootNode;
+    this.animationModule.setup();
+  }
+
+  traverse() {
+    // ...
+  }
+}
+
+const $ = new DOMTraverser({
+  rootNode: document.getElementsByTagName('body'),
+  animationModule() {} // Most of the time, we won't need to animate when traversing.
+  // ...
+});
+
+```
+
+**Good**:
+```javascript
+class DOMTraverser {
+  constructor(settings) {
+    this.settings = settings;
+    this.options = settings.options;
+    this.setup();
+  }
+
+  setup() {
+    this.rootNode = this.settings.rootNode;
+    this.setupOptions();
+  }
+
+  setupOptions() {
+    if (this.options.animationModule) {
+      // ...
+    }
+  }
+
+  traverse() {
+    // ...
+  }
+}
+
+const $ = new DOMTraverser({
+  rootNode: document.getElementsByTagName('body'),
+  options: {
+    animationModule() {}
+  }
+});
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Dependency Inversion Principle (DIP)
+This principle states two essential things:
+1. High-level modules should not depend on low-level modules. Both should
+depend on abstractions.
+2. Abstractions should not depend upon details. Details should depend on
+abstractions.
+
+This can be hard to understand at first, but if you've worked with Angular.js,
+you've seen an implementation of this principle in the form of Dependency
+Injection (DI). While they are not identical concepts, DIP keeps high-level
+modules from knowing the details of its low-level modules and setting them up.
+It can accomplish this through DI. A huge benefit of this is that it reduces
+the coupling between modules. Coupling is a very bad development pattern because
+it makes your code hard to refactor.
+
+As stated previously, JavaScript doesn't have interfaces so the abstractions
+that are depended upon are implicit contracts. That is to say, the methods
+and properties that an object/class exposes to another object/class. In the
+example below, the implicit contract is that any Request module for an
+`InventoryTracker` will have a `requestItems` method.
+
+**Bad:**
+```javascript
+class InventoryRequester {
+  constructor() {
+    this.REQ_METHODS = ['HTTP'];
+  }
+
+  requestItem(item) {
+    // ...
+  }
+}
+
+class InventoryTracker {
+  constructor(items) {
+    this.items = items;
+
+    // BAD: We have created a dependency on a specific request implementation.
+    // We should just have requestItems depend on a request method: `request`
+    this.requester = new InventoryRequester();
+  }
+
+  requestItems() {
+    this.items.forEach((item) => {
+      this.requester.requestItem(item);
+    });
+  }
+}
+
+const inventoryTracker = new InventoryTracker(['apples', 'bananas']);
+inventoryTracker.requestItems();
+```
+
+**Good**:
+```javascript
+class InventoryTracker {
+  constructor(items, requester) {
+    this.items = items;
+    this.requester = requester;
+  }
+
+  requestItems() {
+    this.items.forEach((item) => {
+      this.requester.requestItem(item);
+    });
+  }
+}
+
+class InventoryRequesterV1 {
+  constructor() {
+    this.REQ_METHODS = ['HTTP'];
+  }
+
+  requestItem(item) {
+    // ...
+  }
+}
+
+class InventoryRequesterV2 {
+  constructor() {
+    this.REQ_METHODS = ['WS'];
+  }
+
+  requestItem(item) {
+    // ...
+  }
+}
+
+// By constructing our dependencies externally and injecting them, we can easily
+// substitute our request module for a fancy new one that uses WebSockets.
+const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
+inventoryTracker.requestItems();
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Prefer ES2015/ES6 classes over ES5 plain functions
+It's very difficult to get readable class inheritance, construction, and method
+definitions for classical ES5 classes. If you need inheritance (and be aware
+that you might not), then prefer classes. However, prefer small functions over
+classes until you find yourself needing larger and more complex objects.
+
+**Bad:**
+```javascript
+const Animal = function(age) {
+  if (!(this instanceof Animal)) {
+    throw new Error('Instantiate Animal with `new`');
+  }
+
+  this.age = age;
+};
+
+Animal.prototype.move = function move() {};
+
+const Mammal = function(age, furColor) {
+  if (!(this instanceof Mammal)) {
+    throw new Error('Instantiate Mammal with `new`');
+  }
+
+  Animal.call(this, age);
+  this.furColor = furColor;
+};
+
+Mammal.prototype = Object.create(Animal.prototype);
+Mammal.prototype.constructor = Mammal;
+Mammal.prototype.liveBirth = function liveBirth() {};
+
+const Human = function(age, furColor, languageSpoken) {
+  if (!(this instanceof Human)) {
+    throw new Error('Instantiate Human with `new`');
+  }
+
+  Mammal.call(this, age, furColor);
+  this.languageSpoken = languageSpoken;
+};
+
+Human.prototype = Object.create(Mammal.prototype);
+Human.prototype.constructor = Human;
+Human.prototype.speak = function speak() {};
+```
+
+**Good:**
+```javascript
+class Animal {
+  constructor(age) {
+    this.age = age;
+  }
+
+  move() { /* ... */ }
+}
+
+class Mammal extends Animal {
+  constructor(age, furColor) {
+    super(age);
+    this.furColor = furColor;
+  }
+
+  liveBirth() { /* ... */ }
+}
+
+class Human extends Mammal {
+  constructor(age, furColor, languageSpoken) {
+    super(age, furColor);
+    this.languageSpoken = languageSpoken;
+  }
+
+  speak() { /* ... */ }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Use method chaining
+This pattern is very useful in JavaScript and you see it in many libraries such
+as jQuery and Lodash. It allows your code to be expressive, and less verbose.
+For that reason, I say, use method chaining and take a look at how clean your code
+will be. In your class functions, simply return `this` at the end of every function,
+and you can chain further class methods onto it.
+
+**Bad:**
+```javascript
+class Car {
+  constructor() {
+    this.make = 'Honda';
+    this.model = 'Accord';
+    this.color = 'white';
+  }
+
+  setMake(make) {
+    this.make = make;
+  }
+
+  setModel(model) {
+    this.model = model;
+  }
+
+  setColor(color) {
+    this.color = color;
+  }
+
+  save() {
+    console.log(this.make, this.model, this.color);
+  }
+}
+
+const car = new Car();
+car.setColor('pink');
+car.setMake('Ford');
+car.setModel('F-150');
+car.save();
+```
+
+**Good**:
+```javascript
+class Car {
+  constructor() {
+    this.make = 'Honda';
+    this.model = 'Accord';
+    this.color = 'white';
+  }
+
+  setMake(make) {
+    this.make = make;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  setModel(model) {
+    this.model = model;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  setColor(color) {
+    this.color = color;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  save() {
+    console.log(this.make, this.model, this.color);
+    // NOTE: Returning this for chaining
+    return this;
+  }
+}
+
+const car = new Car()
+  .setColor('pink')
+  .setMake('Ford')
+  .setModel('F-150')
+  .save();
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Prefer composition over inheritance
+As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
+you should prefer composition over inheritance where you can. There are lots of
+good reasons to use inheritance and lots of good reasons to use composition.
+The main point for this maxim is that if your mind instinctively goes for
+inheritance, try to think if composition could model your problem better. In some
+cases it can.
+
+You might be wondering then, "when should I use inheritance?" It
+depends on your problem at hand, but this is a decent list of when inheritance
+makes more sense than composition:
+
+1. Your inheritance represents an "is-a" relationship and not a "has-a"
+relationship (Human->Animal vs. User->UserDetails).
+2. You can reuse code from the base classes (Humans can move like all animals).
+3. You want to make global changes to derived classes by changing a base class.
+(Change the caloric expenditure of all animals when they move).
+
+**Bad:**
+```javascript
+class Employee {
+  constructor(name, email) {
+    this.name = name;
+    this.email = email;
+  }
+
+  // ...
+}
+
+// Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
+class EmployeeTaxData extends Employee {
+  constructor(ssn, salary) {
+    super();
+    this.ssn = ssn;
+    this.salary = salary;
+  }
+
+  // ...
+}
+```
+
+**Good**:
+```javascript
+class EmployeeTaxData {
+  constructor(ssn, salary) {
+    this.ssn = ssn;
+    this.salary = salary;
+  }
+
+  // ...
+}
+
+class Employee {
+  constructor(name, email) {
+    this.name = name;
+    this.email = email;
+  }
+
+  setTaxData(ssn, salary) {
+    this.taxData = new EmployeeTaxData(ssn, salary);
+  }
+  // ...
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+## **Testing**
+Testing is more important than shipping. If you have no tests or an
+inadequate amount, then every time you ship code you won't be sure that you
+didn't break anything. Deciding on what constitutes an adequate amount is up
+to your team, but having 100% coverage (all statements and branches) is how
+you achieve very high confidence and developer peace of mind. This means that
+in addition to having a great testing framework, you also need to use a
+[good coverage tool](http://gotwarlost.github.io/istanbul/).
+
+There's no excuse to not write tests. There's [plenty of good JS test frameworks]
+(http://jstherightway.org/#testing-tools), so find one that your team prefers.
+When you find one that works for your team, then aim to always write tests
+for every new feature/module you introduce. If your preferred method is
+Test Driven Development (TDD), that is great, but the main point is to just
+make sure you are reaching your coverage goals before launching any feature,
+or refactoring an existing one.
+
+### Single concept per test
+
+**Bad:**
+```javascript
+const assert = require('assert');
+
+describe('MakeMomentJSGreatAgain', () => {
+  it('handles date boundaries', () => {
+    let date;
+
+    date = new MakeMomentJSGreatAgain('1/1/2015');
+    date.addDays(30);
+    date.shouldEqual('1/31/2015');
+
+    date = new MakeMomentJSGreatAgain('2/1/2016');
+    date.addDays(28);
+    assert.equal('02/29/2016', date);
+
+    date = new MakeMomentJSGreatAgain('2/1/2015');
+    date.addDays(28);
+    assert.equal('03/01/2015', date);
+  });
+});
+```
+
+**Good**:
+```javascript
+const assert = require('assert');
+
+describe('MakeMomentJSGreatAgain', () => {
+  it('handles 30-day months', () => {
+    const date = new MakeMomentJSGreatAgain('1/1/2015');
+    date.addDays(30);
+    date.shouldEqual('1/31/2015');
+  });
+
+  it('handles leap year', () => {
+    const date = new MakeMomentJSGreatAgain('2/1/2016');
+    date.addDays(28);
+    assert.equal('02/29/2016', date);
+  });
+
+  it('handles non-leap year', () => {
+    const date = new MakeMomentJSGreatAgain('2/1/2015');
+    date.addDays(28);
+    assert.equal('03/01/2015', date);
+  });
+});
+```
+**[⬆ back to top](#table-of-contents)**
+
+## **Concurrency**
+### Use Promises, not callbacks
+Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
+Promises are a built-in global type. Use them!
+
+**Bad:**
+```javascript
+require('request').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response) => {
+  if (requestErr) {
+    console.error(requestErr);
+  } else {
+    require('fs').writeFile('article.html', response.body, (writeErr) => {
+      if (writeErr) {
+        console.error(writeErr);
+      } else {
+        console.log('File written');
+      }
+    });
+  }
+});
+
+```
+
+**Good**:
+```javascript
+require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
+  .then((response) => {
+    return require('fs-promise').writeFile('article.html', response);
+  })
+  .then(() => {
+    console.log('File written');
+  })
+  .catch((err) => {
+    console.error(err);
+  });
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Async/Await are even cleaner than Promises
+Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
+which offer an even cleaner solution. All you need is a function that is prefixed
+in an `async` keyword, and then you can write your logic imperatively without
+a `then` chain of functions. Use this if you can take advantage of ES2017/ES8 features
+today!
+
+**Bad:**
+```javascript
+require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
+  .then((response) => {
+    return require('fs-promise').writeFile('article.html', response);
+  })
+  .then(() => {
+    console.log('File written');
+  })
+  .catch((err) => {
+    console.error(err);
+  });
+
+```
+
+**Good**:
+```javascript
+async function getCleanCodeArticle() {
+  try {
+    const response = await require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin');
+    await require('fs-promise').writeFile('article.html', response);
+    console.log('File written');
+  } catch(err) {
+    console.error(err);
+  }
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+## **Error Handling**
+Thrown errors are a good thing! They mean the runtime has successfully
+identified when something in your program has gone wrong and it's letting
+you know by stopping function execution on the current stack, killing the
+process (in Node), and notifying you in the console with a stack trace.
+
+### Don't ignore caught errors
+Doing nothing with a caught error doesn't give you the ability to ever fix
+or react to said error. Logging the error to the console (`console.log`)
+isn't much better as often times it can get lost in a sea of things printed
+to the console. If you wrap any bit of code in a `try/catch` it means you
+think an error may occur there and therefore you should have a plan,
+or create a code path, for when it occurs.
+
+**Bad:**
+```javascript
+try {
+  functionThatMightThrow();
+} catch (error) {
+  console.log(error);
+}
+```
+
+**Good:**
+```javascript
+try {
+  functionThatMightThrow();
+} catch (error) {
+  // One option (more noisy than console.log):
+  console.error(error);
+  // Another option:
+  notifyUserOfError(error);
+  // Another option:
+  reportErrorToService(error);
+  // OR do all three!
+}
+```
+
+### Don't ignore rejected promises
+For the same reason you shouldn't ignore caught errors
+from `try/catch`.
+
+**Bad:**
+```javascript
+getdata()
+.then((data) => {
+  functionThatMightThrow(data);
+})
+.catch((error) => {
+  console.log(error);
+});
+```
+
+**Good:**
+```javascript
+getdata()
+.then((data) => {
+  functionThatMightThrow(data);
+})
+.catch((error) => {
+  // One option (more noisy than console.log):
+  console.error(error);
+  // Another option:
+  notifyUserOfError(error);
+  // Another option:
+  reportErrorToService(error);
+  // OR do all three!
+});
+```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## **Formatting**
+Formatting is subjective. Like many rules herein, there is no hard and fast
+rule that you must follow. The main point is DO NOT ARGUE over formatting.
+There are [tons of tools](http://standardjs.com/rules.html) to automate this.
+Use one! It's a waste of time and money for engineers to argue over formatting.
+
+For things that don't fall under the purview of automatic formatting
+(indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
+for some guidance.
+
+### Use consistent capitalization
+JavaScript is untyped, so capitalization tells you a lot about your variables,
+functions, etc. These rules are subjective, so your team can choose whatever
+they want. The point is, no matter what you all choose, just be consistent.
+
+**Bad:**
+```javascript
+const DAYS_IN_WEEK = 7;
+const daysInMonth = 30;
+
+const songs = ['Back In Black', 'Stairway to Heaven', 'Hey Jude'];
+const Artists = ['ACDC', 'Led Zeppelin', 'The Beatles'];
+
+function eraseDatabase() {}
+function restore_database() {}
+
+class animal {}
+class Alpaca {}
+```
+
+**Good**:
+```javascript
+const DAYS_IN_WEEK = 7;
+const DAYS_IN_MONTH = 30;
+
+const songs = ['Back In Black', 'Stairway to Heaven', 'Hey Jude'];
+const artists = ['ACDC', 'Led Zeppelin', 'The Beatles'];
+
+function eraseDatabase() {}
+function restoreDatabase() {}
+
+class Animal {}
+class Alpaca {}
+```
+**[⬆ back to top](#table-of-contents)**
+
+
+### Function callers and callees should be close
+If a function calls another, keep those functions vertically close in the source
+file. Ideally, keep the caller right above the callee. We tend to read code from
+top-to-bottom, like a newspaper. Because of this, make your code read that way.
+
+**Bad:**
+```javascript
+class PerformanceReview {
+  constructor(employee) {
+    this.employee = employee;
+  }
+
+  lookupPeers() {
+    return db.lookup(this.employee, 'peers');
+  }
+
+  lookupManager() {
+    return db.lookup(this.employee, 'manager');
+  }
+
+  getPeerReviews() {
+    const peers = this.lookupPeers();
+    // ...
+  }
+
+  perfReview() {
+    this.getPeerReviews();
+    this.getManagerReview();
+    this.getSelfReview();
+  }
+
+  getManagerReview() {
+    const manager = this.lookupManager();
+  }
+
+  getSelfReview() {
+    // ...
+  }
+}
+
+const review = new PerformanceReview(user);
+review.perfReview();
+```
+
+**Good**:
+```javascript
+class PerformanceReview {
+  constructor(employee) {
+    this.employee = employee;
+  }
+
+  perfReview() {
+    this.getPeerReviews();
+    this.getManagerReview();
+    this.getSelfReview();
+  }
+
+  getPeerReviews() {
+    const peers = this.lookupPeers();
+    // ...
+  }
+
+  lookupPeers() {
+    return db.lookup(this.employee, 'peers');
+  }
+
+  getManagerReview() {
+    const manager = this.lookupManager();
+  }
+
+  lookupManager() {
+    return db.lookup(this.employee, 'manager');
+  }
+
+  getSelfReview() {
+    // ...
+  }
+}
+
+const review = new PerformanceReview(employee);
+review.perfReview();
+```
+
+**[⬆ back to top](#table-of-contents)**
+
+## **Comments**
+### Only comment things that have business logic complexity.
+Comments are an apology, not a requirement. Good code *mostly* documents itself.
+
+**Bad:**
+```javascript
+function hashIt(data) {
+  // The hash
+  let hash = 0;
+
+  // Length of string
+  const length = data.length;
+
+  // Loop through every character in data
+  for (let i = 0; i < length; i++) {
+    // Get character code.
+    const char = data.charCodeAt(i);
+    // Make the hash
+    hash = ((hash << 5) - hash) + char;
+    // Convert to 32-bit integer
+    hash &= hash;
+  }
+}
+```
+
+**Good**:
+```javascript
+
+function hashIt(data) {
+  let hash = 0;
+  const length = data.length;
+
+  for (let i = 0; i < length; i++) {
+    const char = data.charCodeAt(i);
+    hash = ((hash << 5) - hash) + char;
+
+    // Convert to 32-bit integer
+    hash &= hash;
+  }
+}
+
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Don't leave commented out code in your codebase
+Version control exists for a reason. Leave old code in your history.
+
+**Bad:**
+```javascript
+doStuff();
+// doOtherStuff();
+// doSomeMoreStuff();
+// doSoMuchStuff();
+```
+
+**Good**:
+```javascript
+doStuff();
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Don't have journal comments
+Remember, use version control! There's no need for dead code, commented code,
+and especially journal comments. Use `git log` to get history!
+
+**Bad:**
+```javascript
+/**
+ * 2016-12-20: Removed monads, didn't understand them (RM)
+ * 2016-10-01: Improved using special monads (JP)
+ * 2016-02-03: Removed type-checking (LI)
+ * 2015-03-14: Added combine with type-checking (JR)
+ */
+function combine(a, b) {
+  return a + b;
+}
+```
+
+**Good**:
+```javascript
+function combine(a, b) {
+  return a + b;
+}
+```
+**[⬆ back to top](#table-of-contents)**
+
+### Avoid positional markers
+They usually just add noise. Let the functions and variable names along with the
+proper indentation and formatting give the visual structure to your code.
+
+**Bad:**
+```javascript
+////////////////////////////////////////////////////////////////////////////////
+// Scope Model Instantiation
+////////////////////////////////////////////////////////////////////////////////
+$scope.model = {
+  menu: 'foo',
+  nav: 'bar'
+};
+
+////////////////////////////////////////////////////////////////////////////////
+// Action setup
+////////////////////////////////////////////////////////////////////////////////
+const actions = function() {
+  // ...
+};
+```
+
+**Good**:
+```javascript
+$scope.model = {
+  menu: 'foo',
+  nav: 'bar'
+};
+
+const actions = function() {
+  // ...
+};
+```
+**[⬆ back to top](#table-of-contents)**

From df434cfd1d680b08ee10cbbe7d7117a71604c44c Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Tue, 17 Jan 2017 07:08:41 +0800
Subject: [PATCH 02/54] try toc

---
 README-zh-CN.md | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index c612ec5a..746f827e 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1,18 +1,18 @@
-# clean-code-javascript
-
-## Table of Contents
-  1. [Introduction](#introduction)
-  2. [Variables](#variables)
-  3. [Functions](#functions)
-  4. [Objects and Data Structures](#objects-and-data-structures)
-  5. [Classes](#classes)
-  6. [Testing](#testing)
+# 代码整洁的 JavaScript
+
+## 目录
+  1. [简介](#简介)
+  2. [变量](#variables)
+  3. [函数](#functions)
+  4. [对象和数据结构](#objects-and-data-structures)
+  5. [类](#classes)
+  6. [测试](#testing)
   7. [Concurrency](#concurrency)
-  8. [Error Handling](#error-handling)
-  9. [Formatting](#formatting)
-  10. [Comments](#comments)
+  8. [错误处理](#error-handling)
+  9. [格式化](#formatting)
+  10. [评论](#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)
 

From 7461a090061538137ecc6aee72e27f712d6cb74e Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Tue, 17 Jan 2017 07:15:31 +0800
Subject: [PATCH 03/54] back to top

---
 README-zh-CN.md | 88 ++++++++++++++++++++++++-------------------------
 1 file changed, 44 insertions(+), 44 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 746f827e..d280658c 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -51,7 +51,7 @@ const yyyymmdstr = moment().format('YYYY/MM/DD');
 ```javascript
 const currentDate = moment().format('YYYY/MM/DD');
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Use the same vocabulary for the same type of variable
 
@@ -66,7 +66,7 @@ getCustomerRecord();
 ```javascript
 getUser();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Use searchable names
 We will read more code than we will ever write. It's important that the code we
@@ -92,7 +92,7 @@ const MILLISECONDS_IN_A_DAY = 86400000;
 setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Use explanatory variables
 **Bad:**
@@ -109,7 +109,7 @@ const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
 const [, city, zipCode] = address.match(cityZipCodeRegex) || [];
 saveCityZipCode(city, zipCode);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid Mental Mapping
 Explicit is better than implicit.
@@ -140,7 +140,7 @@ locations.forEach((location) => {
   dispatch(location);
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Don't add unneeded context
 If your class/object name tells you something, don't repeat that in your
@@ -171,7 +171,7 @@ function paintCar(car) {
   car.color = 'Red';
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Use default arguments instead of short circuiting or conditionals
 
@@ -191,7 +191,7 @@ function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
 }
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **Functions**
 ### Function arguments (2 or fewer ideally)
@@ -231,7 +231,7 @@ function createMenu(config) {
 }
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Functions should do one thing
@@ -266,7 +266,7 @@ function isClientActive(client) {
   return clientRecord.isActive();
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Function names should say what they do
 
@@ -291,7 +291,7 @@ function addMonthToDate(month, date) {
 const date = new Date();
 addMonthToDate(1, date);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Functions should only be one level of abstraction
 When you have more than one level of abstraction your function is usually
@@ -359,7 +359,7 @@ function parseBetterJSAlternative(code) {
   });
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Remove duplicate code
 Do your absolute best to avoid duplicate code. Duplicate code is bad because it
@@ -439,7 +439,7 @@ function showList(employees) {
   });
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Set default objects with Object.assign
 
@@ -485,7 +485,7 @@ function createMenu(config) {
 
 createMenu(menuConfig);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Don't use flags as function parameters
@@ -512,7 +512,7 @@ function createTempFile(name) {
   createFile(`./temp/${name}`);
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid Side Effects
 A function produces a side effect if it does anything other than take a value in
@@ -557,7 +557,7 @@ const newName = splitIntoFirstAndLastName(name);
 console.log(name); // 'Ryan McDermott';
 console.log(newName); // ['Ryan', 'McDermott'];
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Don't write to global functions
 Polluting globals is a bad practice in JavaScript because you could clash with another
@@ -587,7 +587,7 @@ class SuperArray extends Array {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Favor functional programming over imperative programming
 JavaScript isn't a functional language in the way that Haskell is, but it has
@@ -641,7 +641,7 @@ const totalOutput = programmerOutput
   .map((programmer) => programmer.linesOfCode)
   .reduce((acc, linesOfCode) => acc + linesOfCode, 0);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Encapsulate conditionals
 
@@ -662,7 +662,7 @@ if (shouldShowSpinner(fsmInstance, listNodeInstance)) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid negative conditionals
 
@@ -687,7 +687,7 @@ if (isDOMNodePresent(node)) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid conditionals
 This seems like an impossible task. Upon first hearing this, most people say,
@@ -743,7 +743,7 @@ class Cessna extends Airplane {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid type-checking (part 1)
 JavaScript is untyped, which means your functions can take any type of argument.
@@ -768,7 +768,7 @@ function travelToTexas(vehicle) {
   vehicle.move(this.currentLocation, new Location('texas'));
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid type-checking (part 2)
 If you are working with basic primitive values like strings, integers, and arrays,
@@ -799,7 +799,7 @@ function combine(val1, val2) {
   return val1 + val2;
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Don't over-optimize
 Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
@@ -824,7 +824,7 @@ for (let i = 0; i < list.length; i++) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Remove dead code
 Dead code is just as bad as duplicate code. There's no reason to keep it in
@@ -855,7 +855,7 @@ function newRequestModule(url) {
 const req = newRequestModule;
 inventoryTracker('apples', req, 'www.inventory-awesome.io');
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **Objects and Data Structures**
 ### Use getters and setters
@@ -921,7 +921,7 @@ bankAccount.balance -= shoesPrice;
 let balance = bankAccount.balance;
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Make objects have private members
@@ -957,7 +957,7 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 delete employee.name;
 console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ## **Classes**
@@ -1016,7 +1016,7 @@ class UserSettings {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Open/Closed Principle (OCP)
 As stated by Bertrand Meyer, "software entities (classes, modules, functions,
@@ -1103,7 +1103,7 @@ class HttpRequester {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Liskov Substitution Principle (LSP)
@@ -1240,7 +1240,7 @@ function renderLargeShapes(shapes) {
 const shapes = [new Rectangle(), new Rectangle(), new Square()];
 renderLargeShapes(shapes);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Interface Segregation Principle (ISP)
 JavaScript doesn't have interfaces so this principle doesn't apply as strictly
@@ -1314,7 +1314,7 @@ const $ = new DOMTraverser({
   }
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Dependency Inversion Principle (DIP)
 This principle states two essential things:
@@ -1409,7 +1409,7 @@ class InventoryRequesterV2 {
 const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
 inventoryTracker.requestItems();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Prefer ES2015/ES6 classes over ES5 plain functions
 It's very difficult to get readable class inheritance, construction, and method
@@ -1484,7 +1484,7 @@ class Human extends Mammal {
   speak() { /* ... */ }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Use method chaining
@@ -1567,7 +1567,7 @@ const car = new Car()
   .setModel('F-150')
   .save();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Prefer composition over inheritance
 As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
@@ -1633,7 +1633,7 @@ class Employee {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **Testing**
 Testing is more important than shipping. If you have no tests or an
@@ -1701,7 +1701,7 @@ describe('MakeMomentJSGreatAgain', () => {
   });
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **Concurrency**
 ### Use Promises, not callbacks
@@ -1740,7 +1740,7 @@ require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Marti
   });
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Async/Await are even cleaner than Promises
 Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
@@ -1776,7 +1776,7 @@ async function getCleanCodeArticle() {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ## **Error Handling**
@@ -1849,7 +1849,7 @@ getdata()
 });
 ```
 
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ## **Formatting**
@@ -1896,7 +1896,7 @@ function restoreDatabase() {}
 class Animal {}
 class Alpaca {}
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
 ### Function callers and callees should be close
@@ -1982,7 +1982,7 @@ const review = new PerformanceReview(employee);
 review.perfReview();
 ```
 
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **Comments**
 ### Only comment things that have business logic complexity.
@@ -2026,7 +2026,7 @@ function hashIt(data) {
 }
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Don't leave commented out code in your codebase
 Version control exists for a reason. Leave old code in your history.
@@ -2043,7 +2043,7 @@ doStuff();
 ```javascript
 doStuff();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Don't have journal comments
 Remember, use version control! There's no need for dead code, commented code,
@@ -2068,7 +2068,7 @@ function combine(a, b) {
   return a + b;
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Avoid positional markers
 They usually just add noise. Let the functions and variable names along with the
@@ -2103,4 +2103,4 @@ const actions = function() {
   // ...
 };
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**

From c00885cc6d865896e62607812506d9e9558a1448 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Tue, 17 Jan 2017 07:17:44 +0800
Subject: [PATCH 04/54] translate back to top and toc

---
 README-zh-CN.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index d280658c..095da05b 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -7,7 +7,7 @@
   4. [对象和数据结构](#objects-and-data-structures)
   5. [类](#classes)
   6. [测试](#testing)
-  7. [Concurrency](#concurrency)
+  7. [并发](#concurrency)
   8. [错误处理](#error-handling)
   9. [格式化](#formatting)
   10. [评论](#comments)

From e623e0e120031d39359a2e9ae3a062b0a9f49e73 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Thu, 19 Jan 2017 07:05:05 +0800
Subject: [PATCH 05/54] translate introduction

---
 README-zh-CN.md | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 095da05b..aa7ba5a7 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -13,25 +13,35 @@
   10. [评论](#comments)
 
 ## 简介
-![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)
+![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](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.
 
+将源自 Robert C. Martin 的 [*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
+的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个用 JavaScript 来生产可
+读的， 可充用的， 以及可重构的软件的指南。
+
 Not every principle herein has to be strictly followed, and even fewer 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*.
 
+这里的每一项原则都不是必须遵守的， 甚至只有更少的能够被广泛认可。 这些仅仅是指南而已， 但是却是
+*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.
 
+我们的软件工程行业只有短短的 50 年， 依然有很多要我们去学习。 当软件架构与建筑架构一样古老时，
+也许我们将会有硬性的规则去遵守。 而现在， 让这些指南做为你和你的团队生产的 JavaScript 代码的
+质量的标准。
+
 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
@@ -39,6 +49,11 @@ 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
 

From 1373345d166e7d42629081a3f2c5f309256ee5a7 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Thu, 19 Jan 2017 07:30:40 +0800
Subject: [PATCH 06/54] translate variables

---
 README-zh-CN.md | 62 ++++++++++++++++++++++++++++---------------------
 1 file changed, 35 insertions(+), 27 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index aa7ba5a7..7b2d1111 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2,7 +2,7 @@
 
 ## 目录
   1. [简介](#简介)
-  2. [变量](#variables)
+  2. [变量](#变量)
   3. [函数](#functions)
   4. [对象和数据结构](#objects-and-data-structures)
   5. [类](#classes)
@@ -54,36 +54,37 @@ improvement. Beat up the code instead!
 和搭档们一起审查代码时清除那些不完善之处。 不要因为最初需要改善的草稿代码而自责， 而是对那些代
 码下手。
 
-## **Variables**
-### Use meaningful and pronounceable variable names
+## **变量**
+### 使用有意义并且可读的变量名称
 
-**Bad:**
+**不好的：**
 ```javascript
 const yyyymmdstr = moment().format('YYYY/MM/DD');
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const currentDate = moment().format('YYYY/MM/DD');
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use the same vocabulary for the same type of variable
+### 为相同类型的变量使用相同的词汇
 
-**Bad:**
+**不好的：**
 ```javascript
 getUserInfo();
 getClientData();
 getCustomerRecord();
 ```
 
-**Good**:
+**好的：**
 ```javascript
 getUser();
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use searchable names
+### 使用可搜索的名称
+
 We will read more code than we will ever write. It's important that the code we
 do write is readable and searchable. By *not* naming variables that end up
 being meaningful for understanding our program, we hurt our readers.
@@ -92,16 +93,21 @@ Make your names searchable. Tools like
 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
 can help identify unnamed constants.
 
-**Bad:**
+我们要阅读的代码比要写的代码多得多， 所以我们写出的代码的可读性和可搜索性是很重要的。 使用没有
+意义的变量名将会导致我们的程序难于理解， 将会伤害我们的读者， 所以请使用可搜索的变量名。 类似
+[buddy.js](https://github.com/danielstjules/buddy.js) 和 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
+的工具可以帮助我们找到未命名的常量。
+
+**不好的：**
 ```javascript
-// What the heck is 86400000 for?
+// 艹， 86400000 是什么鬼？
 setTimeout(blastOff, 86400000);
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
-// Declare them as capitalized `const` globals.
+// 将它们声明为全局常量 `const` 。
 const MILLISECONDS_IN_A_DAY = 86400000;
 
 setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
@@ -109,15 +115,15 @@ setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use explanatory variables
-**Bad:**
+### 使用解释性的变量
+**不好的：**
 ```javascript
 const address = 'One Infinite Loop, Cupertino 95014';
 const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
 saveCityZipCode(address.match(cityZipCodeRegex)[1], address.match(cityZipCodeRegex)[2]);
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const address = 'One Infinite Loop, Cupertino 95014';
 const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
@@ -126,10 +132,10 @@ saveCityZipCode(city, zipCode);
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid Mental Mapping
-Explicit is better than implicit.
+### 避免心理映射
+显示比隐式更好
 
-**Bad:**
+**不好的：**
 ```javascript
 const locations = ['Austin', 'New York', 'San Francisco'];
 locations.forEach((l) => {
@@ -138,12 +144,12 @@ locations.forEach((l) => {
   // ...
   // ...
   // ...
-  // Wait, what is `l` for again?
+  // 等等， `l` 是啥？
   dispatch(l);
 });
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const locations = ['Austin', 'New York', 'San Francisco'];
 locations.forEach((location) => {
@@ -157,11 +163,13 @@ locations.forEach((location) => {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't add unneeded context
+### 不添加不必要的上下文
 If your class/object name tells you something, don't repeat that in your
 variable name.
 
-**Bad:**
+如果你的类名/对象名有意义， 不要在变量名上再重复。
+
+**不好的：**
 ```javascript
 const Car = {
   carMake: 'Honda',
@@ -174,7 +182,7 @@ function paintCar(car) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const Car = {
   make: 'Honda',
@@ -188,9 +196,9 @@ function paintCar(car) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use default arguments instead of short circuiting or conditionals
+### 使用默认变量替代短路运算或条件
 
-**Bad:**
+**不好的：**
 ```javascript
 function createMicrobrewery(name) {
   const breweryName = name || 'Hipster Brew Co.';
@@ -199,7 +207,7 @@ function createMicrobrewery(name) {
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
   // ...

From ae01aaf55db5760b8267b9844916cf07eaaac7d9 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 16:27:52 +0800
Subject: [PATCH 07/54] trans late part functions

---
 README-zh-CN.md | 134 +++++++++++++++++++++++++++++++++++-------------
 1 file changed, 99 insertions(+), 35 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 7b2d1111..a1a59003 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -3,7 +3,7 @@
 ## 目录
   1. [简介](#简介)
   2. [变量](#变量)
-  3. [函数](#functions)
+  3. [函数](#函数)
   4. [对象和数据结构](#objects-and-data-structures)
   5. [类](#classes)
   6. [测试](#testing)
@@ -216,31 +216,43 @@ function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Functions**
-### Function arguments (2 or fewer ideally)
+## **函数**
+
+### 函数参数 (两个以下最理想)
+
 Limiting the amount of function parameters is incredibly important because it
 makes testing your function easier. Having more than three leads to a
 combinatorial explosion where you have to test tons of different cases with
 each separate argument.
 
+限制函数参数的个数是非常重要的， 因为这样将使你的函数容易进行测试。 一旦超过三个参数将会导致组
+合爆炸， 因为你不得不编写大量针对单个参数的测试用例。
+
 Zero arguments is the ideal case. One or two arguments is ok, and three should
 be avoided. Anything more than that should be consolidated. Usually, if you have
 more than two arguments then your function is trying to do too much. In cases
 where it's not, most of the time a higher-level object will suffice as an
 argument.
 
+没有参数是最理想的， 一个或者两个参数也是可以的， 三个参数应该避免， 超过三个应该被重构。 通常，
+如果你有一个超过两个函数的参数， 那就意味着你的函数尝试做太多的事情。 如果不是， 多数情况下一个
+更高级对象可能会满足需求。
+
 Since JavaScript allows us to make objects on the fly, without a lot of class
 boilerplate, you can use an object if you are finding yourself needing a
 lot of arguments.
 
-**Bad:**
+由于 JavaScript 允许我们不定义类型/模板就可以创建对象， 当你发现你自己需要大量的参数时， 你
+可以使用一个对象。
+
+**不好的：**
 ```javascript
 function createMenu(title, body, buttonText, cancellable) {
   // ...
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const menuConfig = {
   title: 'Foo',
@@ -257,14 +269,19 @@ function createMenu(config) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Functions should do one thing
+### 函数应当只做一件事情
+
 This is by far the most important rule in software engineering. When functions
 do more than one thing, they are harder to compose, test, and reason about.
 When you can isolate a function to just one action, they can be refactored
 easily and your code will read much cleaner. If you take nothing else away from
 this guide other than this, you'll be ahead of many developers.
 
-**Bad:**
+这是软件工程中最重要的一条规则， 当函数需要做更多的事情时， 他们将会更难进行编写、 测试和推理。
+当你能将一个函数隔离到只有一个动作， 他们将能够被容易的进行重构并且你的代码将会更容易阅读。 如
+果你严格遵守本指南中的这一条， 你将会领先于许多开发者。
+
+**不好的：**
 ```javascript
 function emailClients(clients) {
   clients.forEach((client) => {
@@ -276,7 +293,7 @@ function emailClients(clients) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function emailClients(clients) {
   clients
@@ -291,9 +308,9 @@ function isClientActive(client) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Function names should say what they do
+### 函数名称应该说明它要做什么
 
-**Bad:**
+**不好的：**
 ```javascript
 function addToDate(date, month) {
   // ...
@@ -301,11 +318,11 @@ function addToDate(date, month) {
 
 const date = new Date();
 
-// It's hard to to tell from the function name what is added
+// 很难从函数名看出加了什么
 addToDate(date, 1);
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function addMonthToDate(month, date) {
   // ...
@@ -316,12 +333,15 @@ addMonthToDate(1, date);
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Functions should only be one level of abstraction
+### 函数应该只有一个抽象级别
+
 When you have more than one level of abstraction your function is usually
 doing too much. Splitting up functions leads to reusability and easier
 testing.
 
-**Bad:**
+当在你的函数中有多于一个抽象级别时， 你的函数通常做了太多事情。 拆分函数将会提升重用性和测试性。
+
+**不好的：**
 ```javascript
 function parseBetterJSAlternative(code) {
   const REGEXES = [
@@ -347,7 +367,7 @@ function parseBetterJSAlternative(code) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function tokenize(code) {
   const REGEXES = [
@@ -384,29 +404,45 @@ function parseBetterJSAlternative(code) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Remove duplicate code
+### 移除冗余代码
+
 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
 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:**
+让这个抽象正确是关键的， 这是为什么要你遵循 *Classes* 那一章的 SOLID 的原因。 不好的抽象比冗
+余代码更差， 所以要谨慎行事。 既然已经这么说了， 如果你能够做出一个好的抽象， 才去做。 不要重复
+你自己， 否则你会发现当你要修改一个东西时时刻需要修改多个地方。
+
+**不好的：**
 ```javascript
 function showDeveloperList(developers) {
   developers.forEach((developer) => {
@@ -439,7 +475,7 @@ function showManagerList(managers) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function showList(employees) {
   employees.forEach((employee) => {
@@ -464,9 +500,9 @@ function showList(employees) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Set default objects with Object.assign
+### 使用 Object.assign 设置默认对象
 
-**Bad:**
+**不好的：**
 ```javascript
 const menuConfig = {
   title: null,
@@ -485,7 +521,7 @@ function createMenu(config) {
 createMenu(menuConfig);
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const menuConfig = {
   title: 'Order',
@@ -511,10 +547,15 @@ createMenu(menuConfig);
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Don't use flags as function parameters
-Flags tell your user that this function does more than one thing. Functions should do one thing. Split out your functions if they are following different code paths based on a boolean.
+### 不要使用标记位做为函数参数
+Flags tell your user that this function does more than one thing. Functions
+should do one thing. Split out your functions if they are following different
+code paths based on a boolean.
 
-**Bad:**
+标记位是告诉你的用户这个函数做了不只一件事情。 函数应该只做一件事情。 如果你的函数因为一个布尔值
+出现不同的代码路径， 请拆分它们。
+
+**不好的：**
 ```javascript
 function createFile(name, temp) {
   if (temp) {
@@ -525,7 +566,7 @@ function createFile(name, temp) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function createFile(name) {
   fs.create(name);
@@ -537,26 +578,39 @@ function createTempFile(name) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid Side Effects
+### 避免副作用
 A function produces a side effect if it does anything other than take a value in
 and return another value or values. A side effect could be writing to a file,
 modifying some global variable, or accidentally wiring all your money to a
 stranger.
 
+如果一个函数做了除接受一个值然后返回一个值或多个值之外的任何事情， 它将会产生副作用， 它可能是
+写入一个文件， 修改一个全局变量， 或者意外的把你所有的钱连接到一个陌生人那里。
+
 Now, you do need to have side effects in a program on occasion. Like the previous
 example, you might need to write to a file. What you want to do is to
 centralize where you are doing this. Don't have several functions and classes
 that write to a particular file. Have one service that does it. One and only one.
 
+现在在你的程序中确实偶尔需要副作用， 就像上面的代码， 你也许需要写入到一个文件， 你需要做的是集
+中化你要做的事情， 不要让多个函数或者类写入一个特定的文件， 用一个服务来实现它， 一个并且只有一
+个。
+
 The main point is to avoid common pitfalls like sharing state between objects
 without any structure, using mutable data types that can be written to by anything,
 and not centralizing where your side effects occur. If you can do this, you will
 be happier than the vast majority of other programmers.
 
-**Bad:**
+重点是避免这些常见的易犯的错误， 比如在对象之间共享状态而不使用任何结构， 使用任何地方都可以写入
+的可变的数据类型， 没有集中化导致副作用。 如果你能做到这些， 那么你将会比其它的码农大军更加幸福。
+
+**不好的：**
 ```javascript
 // Global variable referenced by following function.
-// If we had another function that used this name, now it'd be an array and it could break it.
+// 全局变量被下面的函数引用
+// If we had another function that used this name, now it'd be an array and it
+// could break it.
+// 如果我们有另一个函数使用这个 name ， 现在它应该是一个数组， 这可能会出现错误。
 let name = 'Ryan McDermott';
 
 function splitIntoFirstAndLastName() {
@@ -568,7 +622,7 @@ splitIntoFirstAndLastName();
 console.log(name); // ['Ryan', 'McDermott'];
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function splitIntoFirstAndLastName(name) {
   return name.split(' ');
@@ -582,7 +636,7 @@ console.log(newName); // ['Ryan', 'McDermott'];
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't write to global functions
+### 不要写入全局函数
 Polluting globals is a bad practice in JavaScript because you could clash with another
 library and the user of your API would be none-the-wiser until they get an
 exception in production. Let's think about an example: what if you wanted to
@@ -593,7 +647,14 @@ to do the same thing. What if that other library was just using `diff` to find
 the difference between the first and last elements of an array? This is why it
 would be much better to just use ES2015/ES6 classes and simply extend the `Array` global.
 
-**Bad:**
+污染全局在 JavaScript 中是一个不好的做法， 因为你可能会和另外一个类库冲突， 你的 API 的用户
+可能不够聪明， 直到他们得到在生产环境得到一个异常。 让我们来考虑这样一个例子： 假设你要扩展
+JavaScript 的 原生 `Array` ， 添加一个可以显示两个数组的不同之处的 `diff` 方法， 你可以在
+`Array.prototype` 中写一个新的方法， 但是它可能会和尝试做相同事情的其它类库发生冲突。 如果有
+另外一个类库仅仅使用 `diff` 方法来查找数组的第一个元素和最后一个元素之间的不同之处呢？ 这就是
+为什么使用 ES2015/ES6 的类是一个更好的做法的原因， 只要简单的扩展全局的 `Array` 即可。
+
+**不好的：**
 ```javascript
 Array.prototype.diff = function diff(comparisonArray) {
   const hash = new Set(comparisonArray);
@@ -601,7 +662,7 @@ Array.prototype.diff = function diff(comparisonArray) {
 };
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class SuperArray extends Array {
   diff(comparisonArray) {
@@ -612,12 +673,15 @@ class SuperArray extends Array {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Favor functional programming over imperative programming
+### 函数式编程优于指令式编程
 JavaScript isn't a functional language in the way that Haskell is, but it has
 a functional flavor to it. Functional languages are cleaner and easier to test.
 Favor this style of programming when you can.
 
-**Bad:**
+JavaScript 不是 Haskell 那种方式的函数式语言， 但是它有它的函数式风格。 函数式语言更加简洁
+并且更容易进行测试， 当你可以使用函数式编程风格时请尽情使用。
+
+**不好的：**
 ```javascript
 const programmerOutput = [
   {
@@ -642,7 +706,7 @@ for (let i = 0; i < programmerOutput.length; i++) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const programmerOutput = [
   {

From 95435edeb2f754571dafdf6856e30de0ef0a340b Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 16:29:10 +0800
Subject: [PATCH 08/54] Encapsulate conditionals

---
 README-zh-CN.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index a1a59003..e8beffcd 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -730,16 +730,16 @@ const totalOutput = programmerOutput
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Encapsulate conditionals
+### 封装条件语句
 
-**Bad:**
+**不好的：**
 ```javascript
 if (fsm.state === 'fetching' && isEmpty(listNode)) {
   // ...
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function shouldShowSpinner(fsm, listNode) {
   return fsm.state === 'fetching' && isEmpty(listNode);

From dc08ef3afda2dbb37fe7db852e0c8107d88429f1 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 16:38:18 +0800
Subject: [PATCH 09/54] Avoid negative conditionals

---
 README-zh-CN.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index e8beffcd..9e11a742 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -751,9 +751,9 @@ if (shouldShowSpinner(fsmInstance, listNodeInstance)) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid negative conditionals
+### 避免负面条件
 
-**Bad:**
+**不好的：**
 ```javascript
 function isDOMNodeNotPresent(node) {
   // ...
@@ -764,7 +764,7 @@ if (!isDOMNodeNotPresent(node)) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function isDOMNodePresent(node) {
   // ...

From bbd65e4410060f0721d0e572ef9de643a6f637a5 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 16:48:34 +0800
Subject: [PATCH 10/54] Avoid conditionals

---
 README-zh-CN.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 9e11a742..b6e599bd 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -776,7 +776,7 @@ if (isDOMNodePresent(node)) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid conditionals
+### 避免条件
 This seems like an impossible task. Upon first hearing this, most people say,
 "how am I supposed to do anything without an `if` statement?" The answer is that
 you can use polymorphism to achieve the same task in many cases. The second
@@ -786,7 +786,13 @@ one thing. When you have classes and functions that have `if` statements, you
 are telling your user that your function does more than one thing. Remember,
 just do one thing.
 
-**Bad:**
+这看起来似乎是一个不可能的任务。 第一次听到这个时， 多数人会说： “没有 `if` 语句还能期望我干
+啥呢”， 答案是多数情况下你可以使用多态来完成同样的任务。 第二个问题通常是 “好了， 那么做很棒，
+但是我为什么想要那样做呢”， 答案是我们学到的上一条代码整洁之道的理念： 一个函数应当只做一件事情。
+当你有使用 `if` 语句的类/函数是， 你在告诉你的用户你的函数做了不止一件事情。 记住： 只做一件
+事情。
+
+**不好的：**
 ```javascript
 class Airplane {
   // ...
@@ -803,7 +809,7 @@ class Airplane {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class Airplane {
   // ...

From 0a8077d88ab51a2345cfa7483129521ac6b80a8f Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 17:18:44 +0800
Subject: [PATCH 11/54] Avoid type-checking (part 1)

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index b6e599bd..b0688c7d 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -838,13 +838,16 @@ class Cessna extends Airplane {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid type-checking (part 1)
+### 避免类型检查 (part 1)
 JavaScript is untyped, which means your functions can take any type of argument.
 Sometimes you are bitten by this freedom and it becomes tempting to do
 type-checking in your functions. There are many ways to avoid having to do this.
 The first thing to consider is consistent APIs.
 
-**Bad:**
+JavaScript 是无类型的， 这意味着你的函数能接受任何类型的参数。 但是有时又会被这种自由咬伤，
+于是又尝试在你的函数中做类型检查。 有很多种方式来避免这个， 第一个要考虑的是一致的 API 。
+
+**不好的：**
 ```javascript
 function travelToTexas(vehicle) {
   if (vehicle instanceof Bicycle) {
@@ -855,7 +858,7 @@ function travelToTexas(vehicle) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function travelToTexas(vehicle) {
   vehicle.move(this.currentLocation, new Location('texas'));

From 51fb61105e45382faab89f368e12d79c1e1ca066 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 17:32:24 +0800
Subject: [PATCH 12/54] Avoid type-checking (part 2)

---
 README-zh-CN.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index b0688c7d..c68bbe17 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -866,7 +866,7 @@ function travelToTexas(vehicle) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid type-checking (part 2)
+### 避免类型检查 (part 2)
 If you are working with basic primitive values like strings, integers, and arrays,
 and you can't use polymorphism but you still feel the need to type-check,
 you should consider using TypeScript. It is an excellent alternative to normal
@@ -877,7 +877,13 @@ doesn't make up for the lost readability. Keep your JavaScript clean, write
 good tests, and have good code reviews. Otherwise, do all of that but with
 TypeScript (which, like I said, is a great alternative!).
 
-**Bad:**
+如果你使用原始的字符串、 整数和数组， 并且你不能使用多态， 但是你依然感觉到有类型检查的需要，
+你应该考虑使用 TypeScript 。 它是一个常规 JavaScript 的优秀的替代品， 因为它在标准的 JavaScript
+语法之上为你提供静态类型。 对常规 JavaScript 做人工类型检查的问题是需要大量的冗词来仿造类型安
+全而不缺失可读性。 保持你的 JavaScript 简洁， 编写良好的测试， 并有良好的代码审阅， 否则使用
+TypeScript （就像我说的， 它是一个伟大的替代品）来完成这些。
+
+**不好的：**
 ```javascript
 function combine(val1, val2) {
   if (typeof val1 === 'number' && typeof val2 === 'number' ||
@@ -889,7 +895,7 @@ function combine(val1, val2) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function combine(val1, val2) {
   return val1 + val2;

From 736c7e0c78265cb38642b80f97e9c2301213d479 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 17:47:06 +0800
Subject: [PATCH 13/54] Don't over-optimize

---
 README-zh-CN.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index c68bbe17..48932b77 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -903,24 +903,30 @@ function combine(val1, val2) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't over-optimize
+### 不要过度优化
 Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
 times, if you are optimizing then you are just wasting your time. [There are good
 resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)
 for seeing where optimization is lacking. Target those in the meantime, until
 they are fixed if they can be.
 
-**Bad:**
+现代化浏览器运行时在幕后做大量的优化， 在大多数的时间， 做优化就是在浪费你的时间。 [这些是好的
+资源](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)， 用来
+查看那些地方需要优化。 为这些而优化， 直到他们被修正。
+
+**不好的：**
 ```javascript
 
 // On old browsers, each iteration with uncached `list.length` would be costly
 // because of `list.length` recomputation. In modern browsers, this is optimized.
+// 在旧的浏览器上， 每次循环 `list.length` 都没有被缓存， 会导致不必要的开销， 因为要重新计
+// 算 `list.length` 。 在现代化浏览器上， 这个已经被优化了。
 for (let i = 0, len = list.length; i < len; i++) {
   // ...
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 for (let i = 0; i < list.length; i++) {
   // ...

From 291d6a26b01b98a04e9fc3ffc583070a81648b1b Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sat, 4 Feb 2017 17:50:03 +0800
Subject: [PATCH 14/54] Objects and Data Structures

---
 README-zh-CN.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 48932b77..0e1309c7 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -4,7 +4,7 @@
   1. [简介](#简介)
   2. [变量](#变量)
   3. [函数](#函数)
-  4. [对象和数据结构](#objects-and-data-structures)
+  4. [对象和数据结构](#对象和数据结构)
   5. [类](#classes)
   6. [测试](#testing)
   7. [并发](#concurrency)
@@ -965,7 +965,7 @@ inventoryTracker('apples', req, 'www.inventory-awesome.io');
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Objects and Data Structures**
+## **对象和数据结构**
 ### Use getters and setters
 JavaScript doesn't have interfaces or types so it is very hard to enforce this
 pattern, because we don't have keywords like `public` and `private`. As it is,

From 7ba2ccf0b05cce6d7c63b141bffcc4f374ca0b14 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 09:51:33 +0800
Subject: [PATCH 15/54] Use getters and setters

---
 README-zh-CN.md | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 0e1309c7..afc3e7b8 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -966,13 +966,17 @@ inventoryTracker('apples', req, 'www.inventory-awesome.io');
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **对象和数据结构**
-### Use getters and setters
+### 使用 getters 和 setters
 JavaScript doesn't have interfaces or types so it is very hard to enforce this
 pattern, because we don't have keywords like `public` and `private`. As it is,
 using getters and setters to access data on objects is far better than simply
 looking for a property on an object. "Why?" you might ask. Well, here's an
 unorganized list of reasons why:
 
+JavaScript 没有接口或类型， 所以坚持这个模式是非常困难的， 因为我们没有 `public` 和 `private`
+关键字。 正因为如此， 使用 getters 和 setters 来访问对象上的数据比简单的在一个对象上查找属性
+要好得多。 “为什么？” 你可能会问， 好吧， 原因请看下面的列表：
+
 * When you want to do more beyond getting an object property, you don't have
 to look up and change every accessor in your codebase.
 * Makes adding validation simple when doing a `set`.
@@ -982,8 +986,14 @@ to look up and change every accessor in your codebase.
 * You can lazy load your object's properties, let's say getting it from a
 server.
 
+* 当你想在获取一个对象属性的背后做更多的事情时， 你不需要在代码库中查找和修改每一处访问；
+* 使用 `set` 可以让添加验证变得容易；
+* 封装内部实现；
+* 使用 getting 和 setting 时， 容易添加日志和错误处理；
+* 继承这个类， 你可以重写默认功能；
+* 你可以延迟加载对象的属性， 比如说从服务器获取。
 
-**Bad:**
+**不好的：**
 ```javascript
 class BankAccount {
   constructor() {
@@ -997,7 +1007,7 @@ const bankAccount = new BankAccount();
 bankAccount.balance -= 100;
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class BankAccount {
   constructor(balance = 1000) {

From b7288c47fdb725762f6d2910f3041f58da0751cd Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 09:54:24 +0800
Subject: [PATCH 16/54] Remove dead code

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index afc3e7b8..d360baa3 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -934,12 +934,15 @@ for (let i = 0; i < list.length; i++) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Remove dead code
+### 移除僵尸代码
 Dead code is just as bad as duplicate code. There's no reason to keep it in
 your codebase. If it's not being called, get rid of it! It will still be safe
 in your version history if you still need it.
 
-**Bad:**
+僵死代码和冗余代码同样糟糕。 没有理由在代码库中保存它。 如果它不会被调用， 就删掉它。 当你需要
+它时， 它依然保存在版本历史记录中。
+
+**不好的：**
 ```javascript
 function oldRequestModule(url) {
   // ...
@@ -954,7 +957,7 @@ inventoryTracker('apples', req, 'www.inventory-awesome.io');
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function newRequestModule(url) {
   // ...

From 567abaad3f7f3d2ad39b740a28262fa22ba83117 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 09:58:47 +0800
Subject: [PATCH 17/54] Make objects have private members

---
 README-zh-CN.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index d360baa3..00708c02 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1045,10 +1045,10 @@ let balance = bankAccount.balance;
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Make objects have private members
-This can be accomplished through closures (for ES5 and below).
+### 让对象拥有私有成员
+这个可以通过闭包来实现（针对 ES5 或更低）。
 
-**Bad:**
+**不好的：**
 ```javascript
 
 const Employee = function(name) {
@@ -1065,7 +1065,7 @@ delete employee.name;
 console.log(`Employee name: ${employee.getName()}`); // Employee name: undefined
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const Employee = function (name) {
   this.getName = function getName() {

From 69232f836365292aff974c74ef26dfae17e5b9c4 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 09:59:38 +0800
Subject: [PATCH 18/54] Classes

---
 README-zh-CN.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 00708c02..799d5584 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -5,7 +5,7 @@
   2. [变量](#变量)
   3. [函数](#函数)
   4. [对象和数据结构](#对象和数据结构)
-  5. [类](#classes)
+  5. [类](#类)
   6. [测试](#testing)
   7. [并发](#concurrency)
   8. [错误处理](#error-handling)
@@ -1081,7 +1081,7 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Classes**
+## **类**
 ### Single Responsibility Principle (SRP)
 As stated in Clean Code, "There should never be more than one reason for a class
 to change". It's tempting to jam-pack a class with a lot of functionality, like

From 2dd45c88f7bf17bc5ca06abbfe91ac28957d7967 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 10:41:49 +0800
Subject: [PATCH 19/54] Single Responsibility Principle

---
 README-zh-CN.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 799d5584..0e516eaa 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1082,7 +1082,7 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 
 
 ## **类**
-### Single Responsibility Principle (SRP)
+### 单一职责原则 (SRP)
 As stated in Clean Code, "There should never be more than one reason for a class
 to change". It's tempting to jam-pack a class with a lot of functionality, like
 when you can only take one suitcase on your flight. The issue with this is
@@ -1092,7 +1092,12 @@ It's important because if too much functionality is in one class and you modify
 it can be difficult to understand how that will affect other dependent modules in
 your codebase.
 
-**Bad:**
+正如代码整洁之道所述， “永远不要有超过一个理由来修改一个类”。 给一个类塞满许多功能， 就像你在航
+班上只能带一个行李箱一样， 这样做的问题你的类不会有理想的内聚性， 将会有太多的理由来对它进行修改。
+最小化需要修改一个类的次数时很重要的， 因为如果一个类拥有太多的功能， 一旦你修改它的一小部分，
+将会很难弄清楚会对代码库中的其它模块造成什么影响。
+
+**好的：**
 ```javascript
 class UserSettings {
   constructor(user) {
@@ -1111,7 +1116,7 @@ class UserSettings {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class UserAuth {
   constructor(user) {

From 510212d05a60d7a07b7ed7749f682be77161afbc Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 10:46:20 +0800
Subject: [PATCH 20/54] Open/Closed Principle

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 0e516eaa..bd0cb305 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1144,13 +1144,16 @@ class UserSettings {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Open/Closed Principle (OCP)
+### 开闭原则 (OCP)
 As stated by Bertrand Meyer, "software entities (classes, modules, functions,
 etc.) should be open for extension, but closed for modification." What does that
 mean though? This principle basically states that you should allow users to
 add new functionalities without changing existing code.
 
-**Bad:**
+Bertrand Meyer 说过， “软件实体 (类， 模块， 函数等) 应该为扩展开放， 但是为修改关闭。” 这
+是什么意思呢？ 这个原则基本上说明了你应该允许用户添加功能而不必修改现有的代码。
+
+**不好的：**
 ```javascript
 class AjaxAdapter extends Adapter {
   constructor() {
@@ -1193,7 +1196,7 @@ function makeHttpCall(url) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class AjaxAdapter extends Adapter {
   constructor() {

From 25966b0037ee7d2d96d1158a07ccb25509dee6f4 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 11:05:03 +0800
Subject: [PATCH 21/54] Liskov Substitution Principle

---
 README-zh-CN.md | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index bd0cb305..9d09a4b2 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1235,13 +1235,17 @@ class HttpRequester {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Liskov Substitution Principle (LSP)
+### 里氏代换原则 (LSP)
 This is a scary term for a very simple concept. It's formally defined as "If S
 is a subtype of T, then objects of type T may be replaced with objects of type S
 (i.e., objects of type S may substitute objects of type T) without altering any
 of the desirable properties of that program (correctness, task performed,
 etc.)." That's an even scarier definition.
 
+这是针对一个非常简单的里面的一个恐怖意图， 它的正式定义是： “如果 S 是 T 的一个子类型， 那么类
+型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）儿不需
+要修改目标程序的期望性质 （正确性、 任务执行性等）。” 这甚至是个恐怖的定义。
+
 The best explanation for this is if you have a parent class and a child class,
 then the base class and child class can be used interchangeably without getting
 incorrect results. This might still be confusing, so let's take a look at the
@@ -1249,7 +1253,11 @@ classic Square-Rectangle example. Mathematically, a square is a rectangle, but
 if you model it using the "is-a" relationship via inheritance, you quickly
 get into trouble.
 
-**Bad:**
+最好的解释是， 如果你又一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
+能还有有些疑惑， 让我们来看一下这个经典的正方形与矩形的例子。 从数学上说， 一个正方形是一个矩形，
+但是你用 "is-a" 的关系用继承来实现， 你将很快遇到麻烦。
+
+**不好的：**
 ```javascript
 class Rectangle {
   constructor() {
@@ -1303,7 +1311,7 @@ const rectangles = [new Rectangle(), new Rectangle(), new Square()];
 renderLargeRectangles(rectangles);
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class Shape {
   setColor(color) {

From 63893ecdd9d6a68f9f61988966539bf5f88dd658 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 11:18:24 +0800
Subject: [PATCH 22/54] Interface Segregation Principle

---
 README-zh-CN.md | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 9d09a4b2..c51a438a 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1379,21 +1379,31 @@ renderLargeShapes(shapes);
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Interface Segregation Principle (ISP)
+### 接口隔离原则 (ISP)
 JavaScript doesn't have interfaces so this principle doesn't apply as strictly
 as others. However, it's important and relevant even with JavaScript's lack of
 type system.
 
+JavaScript 没有接口， 所以这个原则不想其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
+型的语言来说， 它依然是重要并且有意义的。
+
 ISP states that "Clients should not be forced to depend upon interfaces that
 they do not use." Interfaces are implicit contracts in JavaScript because of
 duck typing.
 
+接口隔离原则说的是 “客户端不应该强制依赖他们不需要的接口。” 在 JavaScript 这种弱类型语言中，
+接口是隐式的契约。
+
 A good example to look at that demonstrates this principle in JavaScript is for
 classes that require large settings objects. Not requiring clients to setup
 huge amounts of options is beneficial, because most of the time they won't need
 all of the settings. Making them optional helps prevent having a "fat interface".
 
-**Bad:**
+在 JavaScript 中能比较好的说明这个原则的是一个类需要一个巨大的配置对象。 不需要客户端去设置大
+量的选项是有益的， 因为多数情况下他们不需要全部的设置。 让它们变成可选的有助于防止出现一个“胖接
+口”。
+
+**不好的：**
 ```javascript
 class DOMTraverser {
   constructor(settings) {
@@ -1419,7 +1429,7 @@ const $ = new DOMTraverser({
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class DOMTraverser {
   constructor(settings) {

From 58f44d894986a6adc4c2e692aa7c9b066dd2e252 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 11:47:40 +0800
Subject: [PATCH 23/54] Dependency Inversion Principle

---
 README-zh-CN.md | 23 ++++++++++++++++++++---
 1 file changed, 20 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index c51a438a..3f254414 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1463,13 +1463,17 @@ const $ = new DOMTraverser({
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Dependency Inversion Principle (DIP)
+### 依赖反转原则 (DIP)
 This principle states two essential things:
 1. High-level modules should not depend on low-level modules. Both should
 depend on abstractions.
 2. Abstractions should not depend upon details. Details should depend on
 abstractions.
 
+这个原则阐述了两个重要的事情：
+1. 高级模块不应该依赖于低级模块， 两者都应该依赖与抽象；
+2. 抽象不应当依赖于具体实现， 具体实现应当依赖于抽象。
+
 This can be hard to understand at first, but if you've worked with Angular.js,
 you've seen an implementation of this principle in the form of Dependency
 Injection (DI). While they are not identical concepts, DIP keeps high-level
@@ -1478,13 +1482,22 @@ It can accomplish this through DI. A huge benefit of this is that it reduces
 the coupling between modules. Coupling is a very bad development pattern because
 it makes your code hard to refactor.
 
+这个一开始会很难理解， 但是如果你使用过 Angular.js ， 你应该已经看到过通过依赖注入来实现的这
+个原则， 虽然他们不是相同的概念， 依赖反转原则让高级模块远离低级模块的细节和创建， 可以通过 DI
+来实现。 这样做的巨大益处是降低模块间的耦合。 耦合是一个非常糟糕的开发模式， 因为会导致代码难于
+重构。
+
 As stated previously, JavaScript doesn't have interfaces so the abstractions
 that are depended upon are implicit contracts. That is to say, the methods
 and properties that an object/class exposes to another object/class. In the
 example below, the implicit contract is that any Request module for an
 `InventoryTracker` will have a `requestItems` method.
 
-**Bad:**
+如上所述， JavaScript 没有接口， 所以被依赖的抽象是隐式契约。 也就是说， 一个对象/类的方法和
+属性直接暴露给另外一个对象/类。 在下面的例子中， 任何一个 Request 模块的隐式契约 `InventoryTracker`
+将有一个 `requestItems` 方法。
+
+**不好的：**
 ```javascript
 class InventoryRequester {
   constructor() {
@@ -1502,6 +1515,8 @@ class InventoryTracker {
 
     // BAD: We have created a dependency on a specific request implementation.
     // We should just have requestItems depend on a request method: `request`
+    // 不好的： 我们已经创建了一个对请求的具体实现的依赖， 我们只有一个 requestItems 方法依
+    // 赖一个请求方法 'request'
     this.requester = new InventoryRequester();
   }
 
@@ -1516,7 +1531,7 @@ const inventoryTracker = new InventoryTracker(['apples', 'bananas']);
 inventoryTracker.requestItems();
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class InventoryTracker {
   constructor(items, requester) {
@@ -1553,6 +1568,8 @@ class InventoryRequesterV2 {
 
 // By constructing our dependencies externally and injecting them, we can easily
 // substitute our request module for a fancy new one that uses WebSockets.
+// 通过外部创建依赖项并将它们注入， 我们可以轻松的用一个崭新的使用 WebSockets 的请求模块进行
+// 替换。
 const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
 inventoryTracker.requestItems();
 ```

From 8b55e2d9bd805a70a83d8f5f79505884d94d0c00 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 11:59:17 +0800
Subject: [PATCH 24/54] Prefer ES2015/ES6 classes over ES5 plain functions

---
 README-zh-CN.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 3f254414..ee224241 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1575,13 +1575,17 @@ inventoryTracker.requestItems();
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Prefer ES2015/ES6 classes over ES5 plain functions
+### ES2015/ES6 类优先与 ES5 纯函数
 It's very difficult to get readable class inheritance, construction, and method
 definitions for classical ES5 classes. If you need inheritance (and be aware
 that you might not), then prefer classes. However, prefer small functions over
 classes until you find yourself needing larger and more complex objects.
 
-**Bad:**
+很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
+要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
+对象。
+
+**不好的：**
 ```javascript
 const Animal = function(age) {
   if (!(this instanceof Animal)) {
@@ -1620,7 +1624,7 @@ Human.prototype.constructor = Human;
 Human.prototype.speak = function speak() {};
 ```
 
-**Good:**
+**好的**
 ```javascript
 class Animal {
   constructor(age) {

From b4e287cc75d00261517a8a747e3687c073e04fac Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 14:47:38 +0800
Subject: [PATCH 25/54] Use method chaining

---
 README-zh-CN.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index ee224241..8a33ea8c 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1654,15 +1654,19 @@ class Human extends Mammal {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-
-### Use method chaining
+### 使用方法链
 This pattern is very useful in JavaScript and you see it in many libraries such
 as jQuery and Lodash. It allows your code to be expressive, and less verbose.
 For that reason, I say, use method chaining and take a look at how clean your code
 will be. In your class functions, simply return `this` at the end of every function,
 and you can chain further class methods onto it.
 
-**Bad:**
+这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
+它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
+会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
+其它方法链在一起。
+
+**不好的：**
 ```javascript
 class Car {
   constructor() {
@@ -1695,7 +1699,7 @@ car.setModel('F-150');
 car.save();
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class Car {
   constructor() {

From 8e442cfc044fdaea4ae0f611d687a51d5bcce81d Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 15:16:33 +0800
Subject: [PATCH 26/54] Prefer composition over inheritance

---
 README-zh-CN.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 8a33ea8c..47f93b89 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1741,7 +1741,7 @@ const car = new Car()
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Prefer composition over inheritance
+### 组合优先于继承
 As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
 you should prefer composition over inheritance where you can. There are lots of
 good reasons to use inheritance and lots of good reasons to use composition.
@@ -1749,16 +1749,29 @@ The main point for this maxim is that if your mind instinctively goes for
 inheritance, try to think if composition could model your problem better. In some
 cases it can.
 
+正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
+你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
+的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
+可以。
+
 You might be wondering then, "when should I use inheritance?" It
 depends on your problem at hand, but this is a decent list of when inheritance
 makes more sense than composition:
 
+那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
+明什么时候继承比组合更好用：
+
 1. Your inheritance represents an "is-a" relationship and not a "has-a"
 relationship (Human->Animal vs. User->UserDetails).
 2. You can reuse code from the base classes (Humans can move like all animals).
 3. You want to make global changes to derived classes by changing a base class.
 (Change the caloric expenditure of all animals when they move).
 
+
+1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
+2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
+3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
+
 **Bad:**
 ```javascript
 class Employee {

From 1460272edd82d49bc9fcd8eaddbf239b2be7431a Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 15:49:44 +0800
Subject: [PATCH 27/54] testing

---
 README-zh-CN.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 47f93b89..8f5b13ed 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -6,7 +6,7 @@
   3. [函数](#函数)
   4. [对象和数据结构](#对象和数据结构)
   5. [类](#类)
-  6. [测试](#testing)
+  6. [测试](#测试)
   7. [并发](#concurrency)
   8. [错误处理](#error-handling)
   9. [格式化](#formatting)
@@ -1772,7 +1772,7 @@ relationship (Human->Animal vs. User->UserDetails).
 2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
 3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
 
-**Bad:**
+**不好的：**
 ```javascript
 class Employee {
   constructor(name, email) {
@@ -1784,6 +1784,7 @@ class Employee {
 }
 
 // Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
+// 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
 class EmployeeTaxData extends Employee {
   constructor(ssn, salary) {
     super();
@@ -1795,7 +1796,7 @@ class EmployeeTaxData extends Employee {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class EmployeeTaxData {
   constructor(ssn, salary) {
@@ -1820,7 +1821,7 @@ class Employee {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Testing**
+## **测试**
 Testing is more important than shipping. If you have no tests or an
 inadequate amount, then every time you ship code you won't be sure that you
 didn't break anything. Deciding on what constitutes an adequate amount is up
@@ -1829,6 +1830,10 @@ you achieve very high confidence and developer peace of mind. This means that
 in addition to having a great testing framework, you also need to use a
 [good coverage tool](http://gotwarlost.github.io/istanbul/).
 
+测试比发布更加重要。 如果你没有测试或者测试不够充分， 每次发布时你就不能确认没有破坏任何事情。
+测试的量由你的团队决定， 但是拥有 100% 的覆盖率(包括所有的语句和分支)是你为什么能达到高度自信
+和内心的平静。 这意味着需要一个额外的伟大的测试框架， 也需要一个好的[覆盖率工具](http://gotwarlost.github.io/istanbul/)。
+
 There's no excuse to not write tests. There's [plenty of good JS test frameworks]
 (http://jstherightway.org/#testing-tools), so find one that your team prefers.
 When you find one that works for your team, then aim to always write tests
@@ -1837,6 +1842,11 @@ Test Driven Development (TDD), that is great, but the main point is to just
 make sure you are reaching your coverage goals before launching any feature,
 or refactoring an existing one.
 
+没有理由不写测试。 这里有[大量的优秀的 JS 测试框架](http://jstherightway.org/#testing-tools)，
+选一个适合你的团队的即可。 当为团队选择了测试框架之后， 接下来的目标是为生产的每一个新的功能／模
+块编写测试。 如果你倾向于测试驱动开发(TDD)， 那就太棒了， 但是要点是确认你在上线任何功能或者重
+构一个现有功能之前， 达到了需要的目标覆盖率。
+
 ### Single concept per test
 
 **Bad:**

From f83e7748571688c626625f469fbbfca4adc8f4e4 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 15:52:37 +0800
Subject: [PATCH 28/54] Single concept per test

---
 README-zh-CN.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 8f5b13ed..4fd08c74 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1847,9 +1847,9 @@ or refactoring an existing one.
 块编写测试。 如果你倾向于测试驱动开发(TDD)， 那就太棒了， 但是要点是确认你在上线任何功能或者重
 构一个现有功能之前， 达到了需要的目标覆盖率。
 
-### Single concept per test
+### 一个测试一个概念
 
-**Bad:**
+**不好的：**
 ```javascript
 const assert = require('assert');
 
@@ -1872,7 +1872,7 @@ describe('MakeMomentJSGreatAgain', () => {
 });
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const assert = require('assert');
 

From 93398bedfe39ec0cc9b266dfcbfe9f67e305f8c1 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 17:46:05 +0800
Subject: [PATCH 29/54] concurrency

---
 README-zh-CN.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 4fd08c74..20686166 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -7,7 +7,7 @@
   4. [对象和数据结构](#对象和数据结构)
   5. [类](#类)
   6. [测试](#测试)
-  7. [并发](#concurrency)
+  7. [并发](#并发)
   8. [错误处理](#error-handling)
   9. [格式化](#formatting)
   10. [评论](#comments)
@@ -1898,7 +1898,7 @@ describe('MakeMomentJSGreatAgain', () => {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Concurrency**
+## **并发**
 ### Use Promises, not callbacks
 Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
 Promises are a built-in global type. Use them!

From 4b5192b06dc51cde64abd111c93d7e3f8fb00498 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 17:47:10 +0800
Subject: [PATCH 30/54] Use Promises, not callbacks

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 20686166..e869891b 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1899,11 +1899,14 @@ describe('MakeMomentJSGreatAgain', () => {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **并发**
-### Use Promises, not callbacks
+### 使用 Promises, 不要使用回调
 Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
 Promises are a built-in global type. Use them!
 
-**Bad:**
+回调不够简洁， 因为他们会产生过多的嵌套。 在 ES2015/ES6 中， Promises 已经是内置的全局类型
+了，使用它们吧！
+
+**不好的：**
 ```javascript
 require('request').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response) => {
   if (requestErr) {
@@ -1921,7 +1924,7 @@ require('request').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (req
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
 require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
   .then((response) => {

From e3bcf8c2074e649f4083964b45f4060fb237122b Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 5 Feb 2017 18:03:01 +0800
Subject: [PATCH 31/54] Async/Await are even cleaner than Promises

---
 README-zh-CN.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index e869891b..f7b665b0 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1940,14 +1940,18 @@ require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Marti
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Async/Await are even cleaner than Promises
+### Async/Await 比 Promises 更加简洁
 Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
 which offer an even cleaner solution. All you need is a function that is prefixed
 in an `async` keyword, and then you can write your logic imperatively without
 a `then` chain of functions. Use this if you can take advantage of ES2017/ES8 features
 today!
 
-**Bad:**
+Promises 是回调的一个非常简洁的替代品， 但是 ES2017/ES8 带来的 async 和 await 提供了一个
+更加简洁的解决方案。 你需要的只是一个前缀为 `async` 关键字的函数， 接下来就可以不需要 `then`
+函数链来编写逻辑了。 如果你能使用 ES2017/ES8 的高级功能的话， 今天就使用它吧！
+
+**不好的：**
 ```javascript
 require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
   .then((response) => {
@@ -1962,7 +1966,7 @@ require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Marti
 
 ```
 
-**Good**:
+**好的：**
 ```javascript
 async function getCleanCodeArticle() {
   try {

From 0d37d16cd3f1d8ddb7e8fcbca84b97461d6248db Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 10 Feb 2017 23:25:39 +0800
Subject: [PATCH 32/54] Error Handling

---
 README-zh-CN.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index f7b665b0..5907a313 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -8,7 +8,7 @@
   5. [类](#类)
   6. [测试](#测试)
   7. [并发](#并发)
-  8. [错误处理](#error-handling)
+  8. [错误处理](#错误处理)
   9. [格式化](#formatting)
   10. [评论](#comments)
 
@@ -1981,12 +1981,15 @@ async function getCleanCodeArticle() {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Error Handling**
+## **错误处理**
 Thrown errors are a good thing! They mean the runtime has successfully
 identified when something in your program has gone wrong and it's letting
 you know by stopping function execution on the current stack, killing the
 process (in Node), and notifying you in the console with a stack trace.
 
+抛出错误是一件好事情！ 他们意味着当你的程序有错时运行时可以成功确认， 并且通过停止执行当前堆栈
+上的函数来让你知道， 结束当前进程（在 Node 中）， 在控制台中用一个堆栈跟踪提示你。
+
 ### Don't ignore caught errors
 Doing nothing with a caught error doesn't give you the ability to ever fix
 or react to said error. Logging the error to the console (`console.log`)

From 0a3931c2ce81be5de9d310948f166d8c00fd953f Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 10 Feb 2017 23:33:41 +0800
Subject: [PATCH 33/54] Don't ignore caught errors

---
 README-zh-CN.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 5907a313..822e246f 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1990,7 +1990,7 @@ process (in Node), and notifying you in the console with a stack trace.
 抛出错误是一件好事情！ 他们意味着当你的程序有错时运行时可以成功确认， 并且通过停止执行当前堆栈
 上的函数来让你知道， 结束当前进程（在 Node 中）， 在控制台中用一个堆栈跟踪提示你。
 
-### Don't ignore caught errors
+### 不要忽略捕捉到的错误
 Doing nothing with a caught error doesn't give you the ability to ever fix
 or react to said error. Logging the error to the console (`console.log`)
 isn't much better as often times it can get lost in a sea of things printed
@@ -1998,7 +1998,11 @@ to the console. If you wrap any bit of code in a `try/catch` it means you
 think an error may occur there and therefore you should have a plan,
 or create a code path, for when it occurs.
 
-**Bad:**
+对捕捉到的错误不做任何处理不能给你修复错误或者响应错误的能力。 向控制台记录错误 (`console.log`)
+也不怎么好， 因为往往会丢失在海量的控制台输出中。 如果你把任意一段代码用 `try/catch` 包装那就
+意味着你想到这里可能会错， 因此你应该有个修复计划， 或者当错误发生时有一个代码路径。
+
+**不好的：**
 ```javascript
 try {
   functionThatMightThrow();
@@ -2007,7 +2011,7 @@ try {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 try {
   functionThatMightThrow();

From 6aff7a82be47109f2ed501b918bb691ee3caec1a Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 10 Feb 2017 23:37:50 +0800
Subject: [PATCH 34/54] Don't ignore rejected promises

---
 README-zh-CN.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 822e246f..1c3ef9c8 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2026,11 +2026,13 @@ try {
 }
 ```
 
-### Don't ignore rejected promises
+### 不要忽略被拒绝的 promise 
 For the same reason you shouldn't ignore caught errors
 from `try/catch`.
 
-**Bad:**
+与你不应忽略来自 `try/catch` 的错误的原因相同。
+
+**不好的：**
 ```javascript
 getdata()
 .then((data) => {
@@ -2041,7 +2043,7 @@ getdata()
 });
 ```
 
-**Good:**
+**好的：**
 ```javascript
 getdata()
 .then((data) => {

From 881061cc67894e469e224b89addd7154991aacec Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 10 Feb 2017 23:38:38 +0800
Subject: [PATCH 35/54] miss spell

---
 README-zh-CN.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 1c3ef9c8..d8799416 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -22,7 +22,7 @@ readable, reusable, and refactorable software in JavaScript.
 
 将源自 Robert C. Martin 的 [*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
 的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个用 JavaScript 来生产可
-读的， 可充用的， 以及可重构的软件的指南。
+读的， 可重用的， 以及可重构的软件的指南。
 
 Not every principle herein has to be strictly followed, and even fewer will be
 universally agreed upon. These are guidelines and nothing more, but they are

From 0d4a32353c7e8d27d1fb1536d96e353304582068 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 12 Feb 2017 22:01:48 +0800
Subject: [PATCH 36/54] formating

---
 README-zh-CN.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index d8799416..f5b5cab1 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -9,7 +9,7 @@
   6. [测试](#测试)
   7. [并发](#并发)
   8. [错误处理](#错误处理)
-  9. [格式化](#formatting)
+  9. [格式化](#格式化)
   10. [评论](#comments)
 
 ## 简介
@@ -2063,16 +2063,22 @@ getdata()
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Formatting**
+## **格式化**
 Formatting is subjective. Like many rules herein, there is no hard and fast
 rule that you must follow. The main point is DO NOT ARGUE over formatting.
 There are [tons of tools](http://standardjs.com/rules.html) to automate this.
 Use one! It's a waste of time and money for engineers to argue over formatting.
 
+格式化是主观的。 就像其它规则一样， 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论， 这
+里有[大量的工具](http://standardjs.com/rules.html)来自动格式化， 使用其中的一个即可！ 因
+为做为工程师去争论格式化就是在浪费时间和金钱。
+
 For things that don't fall under the purview of automatic formatting
 (indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
 for some guidance.
 
+针对自动格式化工具不能涵盖的问题（缩进、 制表符还是空格、 双引号还是单引号等）， 这里有一些指南。
+
 ### Use consistent capitalization
 JavaScript is untyped, so capitalization tells you a lot about your variables,
 functions, etc. These rules are subjective, so your team can choose whatever

From fdae9ad4712d4a5551005ec87b9091859bae018b Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 09:53:15 +0800
Subject: [PATCH 37/54] Use consistent capitalization

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index f5b5cab1..7721a38a 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2079,12 +2079,15 @@ for some guidance.
 
 针对自动格式化工具不能涵盖的问题（缩进、 制表符还是空格、 双引号还是单引号等）， 这里有一些指南。
 
-### Use consistent capitalization
+### 使用一致的大小写
 JavaScript is untyped, so capitalization tells you a lot about your variables,
 functions, etc. These rules are subjective, so your team can choose whatever
 they want. The point is, no matter what you all choose, just be consistent.
 
-**Bad:**
+JavaScript 是无类型的， 所以大小写告诉你关于你的变量、 函数等的很多事情。 这些规则是主观的，
+所以你的团队可以选择他们想要的。 重点是， 不管你们选择了什么， 要保持一致。
+
+**不好的：**
 ```javascript
 const DAYS_IN_WEEK = 7;
 const daysInMonth = 30;
@@ -2099,7 +2102,7 @@ class animal {}
 class Alpaca {}
 ```
 
-**Good**:
+**好的：**
 ```javascript
 const DAYS_IN_WEEK = 7;
 const DAYS_IN_MONTH = 30;

From bb99fbbb07883aec83f1a006b10d353fd586b11c Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 10:43:36 +0800
Subject: [PATCH 38/54] Function callers and callees should be close

---
 README-zh-CN.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 7721a38a..e0340816 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2119,12 +2119,16 @@ class Alpaca {}
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Function callers and callees should be close
+### 函数的调用方与被调用方应该靠近
 If a function calls another, keep those functions vertically close in the source
 file. Ideally, keep the caller right above the callee. We tend to read code from
 top-to-bottom, like a newspaper. Because of this, make your code read that way.
 
-**Bad:**
+如果一个函数调用另一个， 则在代码中这两个函数的竖直位置应该靠近。 理想情况下，保持被调用函数在被
+调用函数的正上方。 我们倾向于从上到下阅读代码， 就像读一章报纸。 由于这个原因， 保持你的代码可
+以按照这种方式阅读。
+
+**不好的：**
 ```javascript
 class PerformanceReview {
   constructor(employee) {
@@ -2163,7 +2167,7 @@ const review = new PerformanceReview(user);
 review.perfReview();
 ```
 
-**Good**:
+**好的：**
 ```javascript
 class PerformanceReview {
   constructor(employee) {

From 725d2b2d149253f9b1bea4fa2d86803f69a511f1 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 10:47:58 +0800
Subject: [PATCH 39/54] comments

---
 README-zh-CN.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index e0340816..4eeca39d 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -10,7 +10,7 @@
   7. [并发](#并发)
   8. [错误处理](#错误处理)
   9. [格式化](#格式化)
-  10. [评论](#comments)
+  10. [评论](#评论)
 
 ## 简介
 ![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](http://www.osnews.com/images/comics/wtfm.jpg)
@@ -2208,7 +2208,7 @@ review.perfReview();
 
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Comments**
+## **评论**
 ### Only comment things that have business logic complexity.
 Comments are an apology, not a requirement. Good code *mostly* documents itself.
 

From ad292694f96c25549ddeb38b2f5627d0990c39cc Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 10:52:01 +0800
Subject: [PATCH 40/54] Only comment things that have business logic complexity

---
 README-zh-CN.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 4eeca39d..a6dc3ef6 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2209,10 +2209,12 @@ review.perfReview();
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **评论**
-### Only comment things that have business logic complexity.
+### 仅仅对包含复杂业务逻辑的东西进行评论
 Comments are an apology, not a requirement. Good code *mostly* documents itself.
 
-**Bad:**
+评论是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
+
+**不好的：**
 ```javascript
 function hashIt(data) {
   // The hash
@@ -2233,7 +2235,7 @@ function hashIt(data) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 
 function hashIt(data) {

From c6972166fb1894c398cc7fa4bcdcd64e3ff4ef34 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 10:54:51 +0800
Subject: [PATCH 41/54] Don't leave commented out code in your codebase

---
 README-zh-CN.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index a6dc3ef6..5fb98d4d 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2254,10 +2254,12 @@ function hashIt(data) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't leave commented out code in your codebase
+### 不要在代码库中保存注释掉的代码
 Version control exists for a reason. Leave old code in your history.
 
-**Bad:**
+因为有版本控制， 把旧的代码留在历史记录即可。
+
+**不好的：**
 ```javascript
 doStuff();
 // doOtherStuff();
@@ -2265,7 +2267,7 @@ doStuff();
 // doSoMuchStuff();
 ```
 
-**Good**:
+**好的：**
 ```javascript
 doStuff();
 ```

From 7c8742b70ca81f2b5cc8c3f0062f21a0637dd2ba Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 11:04:53 +0800
Subject: [PATCH 42/54] Don't have journal comments

---
 README-zh-CN.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 5fb98d4d..93409e06 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2273,11 +2273,14 @@ doStuff();
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't have journal comments
+### 不要有日志式的评论
 Remember, use version control! There's no need for dead code, commented code,
 and especially journal comments. Use `git log` to get history!
 
-**Bad:**
+记住， 使用版本控制！ 不需要僵尸代码， 注释调的代码， 尤其是日志式的评论。 使用 `git log` 来
+获取历史记录。
+
+**不好的：**
 ```javascript
 /**
  * 2016-12-20: Removed monads, didn't understand them (RM)
@@ -2290,7 +2293,7 @@ function combine(a, b) {
 }
 ```
 
-**Good**:
+**好的：**
 ```javascript
 function combine(a, b) {
   return a + b;

From c5c5795e44d0d82911d4ba335e95fb28d2e8ad99 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 11:12:12 +0800
Subject: [PATCH 43/54] Avoid positional markers

---
 README-zh-CN.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 93409e06..3d2e6686 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -2301,11 +2301,13 @@ function combine(a, b) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid positional markers
+### 避免占位符
 They usually just add noise. Let the functions and variable names along with the
 proper indentation and formatting give the visual structure to your code.
 
-**Bad:**
+它们仅仅添加了干扰。 让函数和变量名称与合适的缩进和格式化为你的代码提供视觉结构。
+
+**不好的：**
 ```javascript
 ////////////////////////////////////////////////////////////////////////////////
 // Scope Model Instantiation
@@ -2323,7 +2325,7 @@ const actions = function() {
 };
 ```
 
-**Good**:
+**好的：**
 ```javascript
 $scope.model = {
   menu: 'foo',

From f30fd148ed7ebe83417e97bc909d84f86a0c9f04 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 11:25:22 +0800
Subject: [PATCH 44/54] update code.

---
 README-zh-CN.md | 27 +++------------------------
 1 file changed, 3 insertions(+), 24 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index 3d2e6686..a0805847 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -1324,17 +1324,9 @@ class Shape {
 }
 
 class Rectangle extends Shape {
-  constructor() {
+  constructor(width, height) {
     super();
-    this.width = 0;
-    this.height = 0;
-  }
-
-  setWidth(width) {
     this.width = width;
-  }
-
-  setHeight(height) {
     this.height = height;
   }
 
@@ -1344,12 +1336,8 @@ class Rectangle extends Shape {
 }
 
 class Square extends Shape {
-  constructor() {
+  constructor(length) {
     super();
-    this.length = 0;
-  }
-
-  setLength(length) {
     this.length = length;
   }
 
@@ -1360,21 +1348,12 @@ class Square extends Shape {
 
 function renderLargeShapes(shapes) {
   shapes.forEach((shape) => {
-    switch (shape.constructor.name) {
-      case 'Square':
-        shape.setLength(5);
-        break;
-      case 'Rectangle':
-        shape.setWidth(4);
-        shape.setHeight(5);
-    }
-
     const area = shape.getArea();
     shape.render(area);
   });
 }
 
-const shapes = [new Rectangle(), new Rectangle(), new Square()];
+const shapes = [new Rectangle(4, 5), new Rectangle(4, 5), new Square(5)];
 renderLargeShapes(shapes);
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**

From 861e9367fbb0cbf62157bfce0740a710375c3703 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 11:45:28 +0800
Subject: [PATCH 45/54] add chinese translation link

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1bd20e70..ca7d367e 100644
--- a/README.md
+++ b/README.md
@@ -2166,7 +2166,9 @@ const actions = function() {
 This is also available in other languages:
 
   - ![br](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png) **Brazilian Portuguese**: [fesnt/clean-code-javascript](https://github.com/fesnt/clean-code-javascript)
-  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese**: [alivebao/clean-code-js](https://github.com/alivebao/clean-code-js)
+  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese**:
+    - [alivebao/clean-code-js](https://github.com/alivebao/clean-code-js)
+    - [beginor/clean-code-js](https://github.com/beginor/clean-code-javascript/blob/master/README-zh-CN.md)
   - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [marcbruederlin/clean-code-javascript](https://github.com/marcbruederlin/clean-code-javascript)
   - ![kr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png) **Korean**: [qkraudghgh/clean-code-javascript-ko](https://github.com/qkraudghgh/clean-code-javascript-ko)
   - ![ru](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png) **Russian**:

From 844c42d490d97198d19b6bd2df44681bb6aed115 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Mon, 13 Feb 2017 11:46:07 +0800
Subject: [PATCH 46/54] refact file structor based on origin/master

---
 README-zh-CN.md | 523 +++++++++++++++++++++++++-----------------------
 1 file changed, 271 insertions(+), 252 deletions(-)

diff --git a/README-zh-CN.md b/README-zh-CN.md
index a0805847..17090f51 100644
--- a/README-zh-CN.md
+++ b/README-zh-CN.md
@@ -6,11 +6,13 @@
   3. [函数](#函数)
   4. [对象和数据结构](#对象和数据结构)
   5. [类](#类)
-  6. [测试](#测试)
-  7. [并发](#并发)
-  8. [错误处理](#错误处理)
-  9. [格式化](#格式化)
-  10. [评论](#评论)
+  6. [SOLID](#solid)
+  7. [测试](#测试)
+  8. [并发](#并发)
+  9. [错误处理](#错误处理)
+  10. [格式化](#格式化)
+  11. [评论](#评论)
+  12. [Translation](#translation)
 
 ## 简介
 ![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](http://www.osnews.com/images/comics/wtfm.jpg)
@@ -1082,6 +1084,253 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 
 
 ## **类**
+### ES2015/ES6 类优先与 ES5 纯函数
+It's very difficult to get readable class inheritance, construction, and method
+definitions for classical ES5 classes. If you need inheritance (and be aware
+that you might not), then prefer classes. However, prefer small functions over
+classes until you find yourself needing larger and more complex objects.
+
+很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
+要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
+对象。
+
+**不好的：**
+```javascript
+const Animal = function(age) {
+  if (!(this instanceof Animal)) {
+    throw new Error('Instantiate Animal with `new`');
+  }
+
+  this.age = age;
+};
+
+Animal.prototype.move = function move() {};
+
+const Mammal = function(age, furColor) {
+  if (!(this instanceof Mammal)) {
+    throw new Error('Instantiate Mammal with `new`');
+  }
+
+  Animal.call(this, age);
+  this.furColor = furColor;
+};
+
+Mammal.prototype = Object.create(Animal.prototype);
+Mammal.prototype.constructor = Mammal;
+Mammal.prototype.liveBirth = function liveBirth() {};
+
+const Human = function(age, furColor, languageSpoken) {
+  if (!(this instanceof Human)) {
+    throw new Error('Instantiate Human with `new`');
+  }
+
+  Mammal.call(this, age, furColor);
+  this.languageSpoken = languageSpoken;
+};
+
+Human.prototype = Object.create(Mammal.prototype);
+Human.prototype.constructor = Human;
+Human.prototype.speak = function speak() {};
+```
+
+**好的**
+```javascript
+class Animal {
+  constructor(age) {
+    this.age = age;
+  }
+
+  move() { /* ... */ }
+}
+
+class Mammal extends Animal {
+  constructor(age, furColor) {
+    super(age);
+    this.furColor = furColor;
+  }
+
+  liveBirth() { /* ... */ }
+}
+
+class Human extends Mammal {
+  constructor(age, furColor, languageSpoken) {
+    super(age, furColor);
+    this.languageSpoken = languageSpoken;
+  }
+
+  speak() { /* ... */ }
+}
+```
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+### 使用方法链
+This pattern is very useful in JavaScript and you see it in many libraries such
+as jQuery and Lodash. It allows your code to be expressive, and less verbose.
+For that reason, I say, use method chaining and take a look at how clean your code
+will be. In your class functions, simply return `this` at the end of every function,
+and you can chain further class methods onto it.
+
+这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
+它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
+会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
+其它方法链在一起。
+
+**不好的：**
+```javascript
+class Car {
+  constructor() {
+    this.make = 'Honda';
+    this.model = 'Accord';
+    this.color = 'white';
+  }
+
+  setMake(make) {
+    this.make = make;
+  }
+
+  setModel(model) {
+    this.model = model;
+  }
+
+  setColor(color) {
+    this.color = color;
+  }
+
+  save() {
+    console.log(this.make, this.model, this.color);
+  }
+}
+
+const car = new Car();
+car.setColor('pink');
+car.setMake('Ford');
+car.setModel('F-150');
+car.save();
+```
+
+**好的：**
+```javascript
+class Car {
+  constructor() {
+    this.make = 'Honda';
+    this.model = 'Accord';
+    this.color = 'white';
+  }
+
+  setMake(make) {
+    this.make = make;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  setModel(model) {
+    this.model = model;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  setColor(color) {
+    this.color = color;
+    // NOTE: Returning this for chaining
+    return this;
+  }
+
+  save() {
+    console.log(this.make, this.model, this.color);
+    // NOTE: Returning this for chaining
+    return this;
+  }
+}
+
+const car = new Car()
+  .setColor('pink')
+  .setMake('Ford')
+  .setModel('F-150')
+  .save();
+```
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+### 组合优先于继承
+As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
+you should prefer composition over inheritance where you can. There are lots of
+good reasons to use inheritance and lots of good reasons to use composition.
+The main point for this maxim is that if your mind instinctively goes for
+inheritance, try to think if composition could model your problem better. In some
+cases it can.
+
+正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
+你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
+的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
+可以。
+
+You might be wondering then, "when should I use inheritance?" It
+depends on your problem at hand, but this is a decent list of when inheritance
+makes more sense than composition:
+
+那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
+明什么时候继承比组合更好用：
+
+1. Your inheritance represents an "is-a" relationship and not a "has-a"
+relationship (Human->Animal vs. User->UserDetails).
+2. You can reuse code from the base classes (Humans can move like all animals).
+3. You want to make global changes to derived classes by changing a base class.
+(Change the caloric expenditure of all animals when they move).
+
+
+1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
+2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
+3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
+
+**不好的：**
+```javascript
+class Employee {
+  constructor(name, email) {
+    this.name = name;
+    this.email = email;
+  }
+
+  // ...
+}
+
+// Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
+// 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
+class EmployeeTaxData extends Employee {
+  constructor(ssn, salary) {
+    super();
+    this.ssn = ssn;
+    this.salary = salary;
+  }
+
+  // ...
+}
+```
+
+**好的：**
+```javascript
+class EmployeeTaxData {
+  constructor(ssn, salary) {
+    this.ssn = ssn;
+    this.salary = salary;
+  }
+
+  // ...
+}
+
+class Employee {
+  constructor(name, email) {
+    this.name = name;
+    this.email = email;
+  }
+
+  setTaxData(ssn, salary) {
+    this.taxData = new EmployeeTaxData(ssn, salary);
+  }
+  // ...
+}
+```
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+## **SOLID**
 ### 单一职责原则 (SRP)
 As stated in Clean Code, "There should never be more than one reason for a class
 to change". It's tempting to jam-pack a class with a lot of functionality, like
@@ -1234,7 +1483,6 @@ class HttpRequester {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-
 ### 里氏代换原则 (LSP)
 This is a scary term for a very simple concept. It's formally defined as "If S
 is a subtype of T, then objects of type T may be replaced with objects of type S
@@ -1554,252 +1802,6 @@ inventoryTracker.requestItems();
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### ES2015/ES6 类优先与 ES5 纯函数
-It's very difficult to get readable class inheritance, construction, and method
-definitions for classical ES5 classes. If you need inheritance (and be aware
-that you might not), then prefer classes. However, prefer small functions over
-classes until you find yourself needing larger and more complex objects.
-
-很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
-要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
-对象。
-
-**不好的：**
-```javascript
-const Animal = function(age) {
-  if (!(this instanceof Animal)) {
-    throw new Error('Instantiate Animal with `new`');
-  }
-
-  this.age = age;
-};
-
-Animal.prototype.move = function move() {};
-
-const Mammal = function(age, furColor) {
-  if (!(this instanceof Mammal)) {
-    throw new Error('Instantiate Mammal with `new`');
-  }
-
-  Animal.call(this, age);
-  this.furColor = furColor;
-};
-
-Mammal.prototype = Object.create(Animal.prototype);
-Mammal.prototype.constructor = Mammal;
-Mammal.prototype.liveBirth = function liveBirth() {};
-
-const Human = function(age, furColor, languageSpoken) {
-  if (!(this instanceof Human)) {
-    throw new Error('Instantiate Human with `new`');
-  }
-
-  Mammal.call(this, age, furColor);
-  this.languageSpoken = languageSpoken;
-};
-
-Human.prototype = Object.create(Mammal.prototype);
-Human.prototype.constructor = Human;
-Human.prototype.speak = function speak() {};
-```
-
-**好的**
-```javascript
-class Animal {
-  constructor(age) {
-    this.age = age;
-  }
-
-  move() { /* ... */ }
-}
-
-class Mammal extends Animal {
-  constructor(age, furColor) {
-    super(age);
-    this.furColor = furColor;
-  }
-
-  liveBirth() { /* ... */ }
-}
-
-class Human extends Mammal {
-  constructor(age, furColor, languageSpoken) {
-    super(age, furColor);
-    this.languageSpoken = languageSpoken;
-  }
-
-  speak() { /* ... */ }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用方法链
-This pattern is very useful in JavaScript and you see it in many libraries such
-as jQuery and Lodash. It allows your code to be expressive, and less verbose.
-For that reason, I say, use method chaining and take a look at how clean your code
-will be. In your class functions, simply return `this` at the end of every function,
-and you can chain further class methods onto it.
-
-这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
-它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
-会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
-其它方法链在一起。
-
-**不好的：**
-```javascript
-class Car {
-  constructor() {
-    this.make = 'Honda';
-    this.model = 'Accord';
-    this.color = 'white';
-  }
-
-  setMake(make) {
-    this.make = make;
-  }
-
-  setModel(model) {
-    this.model = model;
-  }
-
-  setColor(color) {
-    this.color = color;
-  }
-
-  save() {
-    console.log(this.make, this.model, this.color);
-  }
-}
-
-const car = new Car();
-car.setColor('pink');
-car.setMake('Ford');
-car.setModel('F-150');
-car.save();
-```
-
-**好的：**
-```javascript
-class Car {
-  constructor() {
-    this.make = 'Honda';
-    this.model = 'Accord';
-    this.color = 'white';
-  }
-
-  setMake(make) {
-    this.make = make;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  setModel(model) {
-    this.model = model;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  setColor(color) {
-    this.color = color;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  save() {
-    console.log(this.make, this.model, this.color);
-    // NOTE: Returning this for chaining
-    return this;
-  }
-}
-
-const car = new Car()
-  .setColor('pink')
-  .setMake('Ford')
-  .setModel('F-150')
-  .save();
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 组合优先于继承
-As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
-you should prefer composition over inheritance where you can. There are lots of
-good reasons to use inheritance and lots of good reasons to use composition.
-The main point for this maxim is that if your mind instinctively goes for
-inheritance, try to think if composition could model your problem better. In some
-cases it can.
-
-正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
-你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
-的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
-可以。
-
-You might be wondering then, "when should I use inheritance?" It
-depends on your problem at hand, but this is a decent list of when inheritance
-makes more sense than composition:
-
-那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
-明什么时候继承比组合更好用：
-
-1. Your inheritance represents an "is-a" relationship and not a "has-a"
-relationship (Human->Animal vs. User->UserDetails).
-2. You can reuse code from the base classes (Humans can move like all animals).
-3. You want to make global changes to derived classes by changing a base class.
-(Change the caloric expenditure of all animals when they move).
-
-
-1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
-2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
-3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
-
-**不好的：**
-```javascript
-class Employee {
-  constructor(name, email) {
-    this.name = name;
-    this.email = email;
-  }
-
-  // ...
-}
-
-// Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
-// 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
-class EmployeeTaxData extends Employee {
-  constructor(ssn, salary) {
-    super();
-    this.ssn = ssn;
-    this.salary = salary;
-  }
-
-  // ...
-}
-```
-
-**好的：**
-```javascript
-class EmployeeTaxData {
-  constructor(ssn, salary) {
-    this.ssn = ssn;
-    this.salary = salary;
-  }
-
-  // ...
-}
-
-class Employee {
-  constructor(name, email) {
-    this.name = name;
-    this.email = email;
-  }
-
-  setTaxData(ssn, salary) {
-    this.taxData = new EmployeeTaxData(ssn, salary);
-  }
-  // ...
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
 ## **测试**
 Testing is more important than shipping. If you have no tests or an
 inadequate amount, then every time you ship code you won't be sure that you
@@ -2316,3 +2318,20 @@ const actions = function() {
 };
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
+
+## Translation
+
+This is also available in other languages:
+
+  - ![br](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png) **Brazilian Portuguese**: [fesnt/clean-code-javascript](https://github.com/fesnt/clean-code-javascript)
+  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese**:
+    - [alivebao/clean-code-js](https://github.com/alivebao/clean-code-js)
+    - [beginor/clean-code-js](https://github.com/beginor/clean-code-javascript/blob/master/README-zh-CN.md)
+  - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [marcbruederlin/clean-code-javascript](https://github.com/marcbruederlin/clean-code-javascript)
+  - ![kr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png) **Korean**: [qkraudghgh/clean-code-javascript-ko](https://github.com/qkraudghgh/clean-code-javascript-ko)
+  - ![ru](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png) **Russian**:
+    - [BoryaMogila/clean-code-javascript-ru/](https://github.com/BoryaMogila/clean-code-javascript-ru/)
+    - [maksugr/clean-code-javascript](https://github.com/maksugr/clean-code-javascript)
+  - ![vi](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png) **Vietnamese**: [hienvd/clean-code-javascript/](https://github.com/hienvd/clean-code-javascript/)
+
+**[⬆ 返回顶部](#代码整洁的-javascript)**

From b8fe8bc395ba14d743ebcdf33f0fbfac020206fc Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Wed, 15 Feb 2017 11:48:03 +0800
Subject: [PATCH 47/54] remove zh-cn temp file.

---
 README-zh-CN.md | 2337 -----------------------------------------------
 1 file changed, 2337 deletions(-)
 delete mode 100644 README-zh-CN.md

diff --git a/README-zh-CN.md b/README-zh-CN.md
deleted file mode 100644
index 17090f51..00000000
--- a/README-zh-CN.md
+++ /dev/null
@@ -1,2337 +0,0 @@
-# 代码整洁的 JavaScript
-
-## 目录
-  1. [简介](#简介)
-  2. [变量](#变量)
-  3. [函数](#函数)
-  4. [对象和数据结构](#对象和数据结构)
-  5. [类](#类)
-  6. [SOLID](#solid)
-  7. [测试](#测试)
-  8. [并发](#并发)
-  9. [错误处理](#错误处理)
-  10. [格式化](#格式化)
-  11. [评论](#评论)
-  12. [Translation](#translation)
-
-## 简介
-![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](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.
-
-将源自 Robert C. Martin 的 [*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
-的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个用 JavaScript 来生产可
-读的， 可重用的， 以及可重构的软件的指南。
-
-Not every principle herein has to be strictly followed, and even fewer 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*.
-
-这里的每一项原则都不是必须遵守的， 甚至只有更少的能够被广泛认可。 这些仅仅是指南而已， 但是却是
-*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.
-
-我们的软件工程行业只有短短的 50 年， 依然有很多要我们去学习。 当软件架构与建筑架构一样古老时，
-也许我们将会有硬性的规则去遵守。 而现在， 让这些指南做为你和你的团队生产的 JavaScript 代码的
-质量的标准。
-
-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!
-
-还有一件事： 知道这些指南并不能马上让你成为一个更加出色的软件开发者， 并且使用它们工作多年也并
-不意味着你不会犯错误。 每一段代码最开始都是草稿， 像湿粘土一样被打造成最终的形态。 最后当我们
-和搭档们一起审查代码时清除那些不完善之处。 不要因为最初需要改善的草稿代码而自责， 而是对那些代
-码下手。
-
-## **变量**
-### 使用有意义并且可读的变量名称
-
-**不好的：**
-```javascript
-const yyyymmdstr = moment().format('YYYY/MM/DD');
-```
-
-**好的：**
-```javascript
-const currentDate = moment().format('YYYY/MM/DD');
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 为相同类型的变量使用相同的词汇
-
-**不好的：**
-```javascript
-getUserInfo();
-getClientData();
-getCustomerRecord();
-```
-
-**好的：**
-```javascript
-getUser();
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用可搜索的名称
-
-We will read more code than we will ever write. It's important that the code we
-do write is readable and searchable. By *not* naming variables that end up
-being meaningful for understanding our program, we hurt our readers.
-Make your names searchable. Tools like
-[buddy.js](https://github.com/danielstjules/buddy.js) and
-[ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
-can help identify unnamed constants.
-
-我们要阅读的代码比要写的代码多得多， 所以我们写出的代码的可读性和可搜索性是很重要的。 使用没有
-意义的变量名将会导致我们的程序难于理解， 将会伤害我们的读者， 所以请使用可搜索的变量名。 类似
-[buddy.js](https://github.com/danielstjules/buddy.js) 和 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
-的工具可以帮助我们找到未命名的常量。
-
-**不好的：**
-```javascript
-// 艹， 86400000 是什么鬼？
-setTimeout(blastOff, 86400000);
-
-```
-
-**好的：**
-```javascript
-// 将它们声明为全局常量 `const` 。
-const MILLISECONDS_IN_A_DAY = 86400000;
-
-setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用解释性的变量
-**不好的：**
-```javascript
-const address = 'One Infinite Loop, Cupertino 95014';
-const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
-saveCityZipCode(address.match(cityZipCodeRegex)[1], address.match(cityZipCodeRegex)[2]);
-```
-
-**好的：**
-```javascript
-const address = 'One Infinite Loop, Cupertino 95014';
-const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
-const [, city, zipCode] = address.match(cityZipCodeRegex) || [];
-saveCityZipCode(city, zipCode);
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免心理映射
-显示比隐式更好
-
-**不好的：**
-```javascript
-const locations = ['Austin', 'New York', 'San Francisco'];
-locations.forEach((l) => {
-  doStuff();
-  doSomeOtherStuff();
-  // ...
-  // ...
-  // ...
-  // 等等， `l` 是啥？
-  dispatch(l);
-});
-```
-
-**好的：**
-```javascript
-const locations = ['Austin', 'New York', 'San Francisco'];
-locations.forEach((location) => {
-  doStuff();
-  doSomeOtherStuff();
-  // ...
-  // ...
-  // ...
-  dispatch(location);
-});
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 不添加不必要的上下文
-If your class/object name tells you something, don't repeat that in your
-variable name.
-
-如果你的类名/对象名有意义， 不要在变量名上再重复。
-
-**不好的：**
-```javascript
-const Car = {
-  carMake: 'Honda',
-  carModel: 'Accord',
-  carColor: 'Blue'
-};
-
-function paintCar(car) {
-  car.carColor = 'Red';
-}
-```
-
-**好的：**
-```javascript
-const Car = {
-  make: 'Honda',
-  model: 'Accord',
-  color: 'Blue'
-};
-
-function paintCar(car) {
-  car.color = 'Red';
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用默认变量替代短路运算或条件
-
-**不好的：**
-```javascript
-function createMicrobrewery(name) {
-  const breweryName = name || 'Hipster Brew Co.';
-  // ...
-}
-
-```
-
-**好的：**
-```javascript
-function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
-  // ...
-}
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **函数**
-
-### 函数参数 (两个以下最理想)
-
-Limiting the amount of function parameters is incredibly important because it
-makes testing your function easier. Having more than three leads to a
-combinatorial explosion where you have to test tons of different cases with
-each separate argument.
-
-限制函数参数的个数是非常重要的， 因为这样将使你的函数容易进行测试。 一旦超过三个参数将会导致组
-合爆炸， 因为你不得不编写大量针对单个参数的测试用例。
-
-Zero arguments is the ideal case. One or two arguments is ok, and three should
-be avoided. Anything more than that should be consolidated. Usually, if you have
-more than two arguments then your function is trying to do too much. In cases
-where it's not, most of the time a higher-level object will suffice as an
-argument.
-
-没有参数是最理想的， 一个或者两个参数也是可以的， 三个参数应该避免， 超过三个应该被重构。 通常，
-如果你有一个超过两个函数的参数， 那就意味着你的函数尝试做太多的事情。 如果不是， 多数情况下一个
-更高级对象可能会满足需求。
-
-Since JavaScript allows us to make objects on the fly, without a lot of class
-boilerplate, you can use an object if you are finding yourself needing a
-lot of arguments.
-
-由于 JavaScript 允许我们不定义类型/模板就可以创建对象， 当你发现你自己需要大量的参数时， 你
-可以使用一个对象。
-
-**不好的：**
-```javascript
-function createMenu(title, body, buttonText, cancellable) {
-  // ...
-}
-```
-
-**好的：**
-```javascript
-const menuConfig = {
-  title: 'Foo',
-  body: 'Bar',
-  buttonText: 'Baz',
-  cancellable: true
-};
-
-function createMenu(config) {
-  // ...
-}
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-### 函数应当只做一件事情
-
-This is by far the most important rule in software engineering. When functions
-do more than one thing, they are harder to compose, test, and reason about.
-When you can isolate a function to just one action, they can be refactored
-easily and your code will read much cleaner. If you take nothing else away from
-this guide other than this, you'll be ahead of many developers.
-
-这是软件工程中最重要的一条规则， 当函数需要做更多的事情时， 他们将会更难进行编写、 测试和推理。
-当你能将一个函数隔离到只有一个动作， 他们将能够被容易的进行重构并且你的代码将会更容易阅读。 如
-果你严格遵守本指南中的这一条， 你将会领先于许多开发者。
-
-**不好的：**
-```javascript
-function emailClients(clients) {
-  clients.forEach((client) => {
-    const clientRecord = database.lookup(client);
-    if (clientRecord.isActive()) {
-      email(client);
-    }
-  });
-}
-```
-
-**好的：**
-```javascript
-function emailClients(clients) {
-  clients
-    .filter(isClientActive)
-    .forEach(email);
-}
-
-function isClientActive(client) {
-  const clientRecord = database.lookup(client);
-  return clientRecord.isActive();
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 函数名称应该说明它要做什么
-
-**不好的：**
-```javascript
-function addToDate(date, month) {
-  // ...
-}
-
-const date = new Date();
-
-// 很难从函数名看出加了什么
-addToDate(date, 1);
-```
-
-**好的：**
-```javascript
-function addMonthToDate(month, date) {
-  // ...
-}
-
-const date = new Date();
-addMonthToDate(1, date);
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 函数应该只有一个抽象级别
-
-When you have more than one level of abstraction your function is usually
-doing too much. Splitting up functions leads to reusability and easier
-testing.
-
-当在你的函数中有多于一个抽象级别时， 你的函数通常做了太多事情。 拆分函数将会提升重用性和测试性。
-
-**不好的：**
-```javascript
-function parseBetterJSAlternative(code) {
-  const REGEXES = [
-    // ...
-  ];
-
-  const statements = code.split(' ');
-  const tokens = [];
-  REGEXES.forEach((REGEX) => {
-    statements.forEach((statement) => {
-      // ...
-    });
-  });
-
-  const ast = [];
-  tokens.forEach((token) => {
-    // lex...
-  });
-
-  ast.forEach((node) => {
-    // parse...
-  });
-}
-```
-
-**好的：**
-```javascript
-function tokenize(code) {
-  const REGEXES = [
-    // ...
-  ];
-
-  const statements = code.split(' ');
-  const tokens = [];
-  REGEXES.forEach((REGEX) => {
-    statements.forEach((statement) => {
-      tokens.push( /* ... */ );
-    });
-  });
-
-  return tokens;
-}
-
-function lexer(tokens) {
-  const ast = [];
-  tokens.forEach((token) => {
-    ast.push( /* ... */ );
-  });
-
-  return ast;
-}
-
-function parseBetterJSAlternative(code) {
-  const tokens = tokenize(code);
-  const ast = lexer(tokens);
-  ast.forEach((node) => {
-    // parse...
-  });
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 移除冗余代码
-
-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
-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.
-
-让这个抽象正确是关键的， 这是为什么要你遵循 *Classes* 那一章的 SOLID 的原因。 不好的抽象比冗
-余代码更差， 所以要谨慎行事。 既然已经这么说了， 如果你能够做出一个好的抽象， 才去做。 不要重复
-你自己， 否则你会发现当你要修改一个东西时时刻需要修改多个地方。
-
-**不好的：**
-```javascript
-function showDeveloperList(developers) {
-  developers.forEach((developer) => {
-    const expectedSalary = developer.calculateExpectedSalary();
-    const experience = developer.getExperience();
-    const githubLink = developer.getGithubLink();
-    const data = {
-      expectedSalary,
-      experience,
-      githubLink
-    };
-
-    render(data);
-  });
-}
-
-function showManagerList(managers) {
-  managers.forEach((manager) => {
-    const expectedSalary = manager.calculateExpectedSalary();
-    const experience = manager.getExperience();
-    const portfolio = manager.getMBAProjects();
-    const data = {
-      expectedSalary,
-      experience,
-      portfolio
-    };
-
-    render(data);
-  });
-}
-```
-
-**好的：**
-```javascript
-function showList(employees) {
-  employees.forEach((employee) => {
-    const expectedSalary = employee.calculateExpectedSalary();
-    const experience = employee.getExperience();
-
-    let portfolio = employee.getGithubLink();
-
-    if (employee.type === 'manager') {
-      portfolio = employee.getMBAProjects();
-    }
-
-    const data = {
-      expectedSalary,
-      experience,
-      portfolio
-    };
-
-    render(data);
-  });
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用 Object.assign 设置默认对象
-
-**不好的：**
-```javascript
-const menuConfig = {
-  title: null,
-  body: 'Bar',
-  buttonText: null,
-  cancellable: true
-};
-
-function createMenu(config) {
-  config.title = config.title || 'Foo';
-  config.body = config.body || 'Bar';
-  config.buttonText = config.buttonText || 'Baz';
-  config.cancellable = config.cancellable === undefined ? config.cancellable : true;
-}
-
-createMenu(menuConfig);
-```
-
-**好的：**
-```javascript
-const menuConfig = {
-  title: 'Order',
-  // User did not include 'body' key
-  buttonText: 'Send',
-  cancellable: true
-};
-
-function createMenu(config) {
-  config = Object.assign({
-    title: 'Foo',
-    body: 'Bar',
-    buttonText: 'Baz',
-    cancellable: true
-  }, config);
-
-  // config now equals: {title: "Order", body: "Bar", buttonText: "Send", cancellable: true}
-  // ...
-}
-
-createMenu(menuConfig);
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-### 不要使用标记位做为函数参数
-Flags tell your user that this function does more than one thing. Functions
-should do one thing. Split out your functions if they are following different
-code paths based on a boolean.
-
-标记位是告诉你的用户这个函数做了不只一件事情。 函数应该只做一件事情。 如果你的函数因为一个布尔值
-出现不同的代码路径， 请拆分它们。
-
-**不好的：**
-```javascript
-function createFile(name, temp) {
-  if (temp) {
-    fs.create(`./temp/${name}`);
-  } else {
-    fs.create(name);
-  }
-}
-```
-
-**好的：**
-```javascript
-function createFile(name) {
-  fs.create(name);
-}
-
-function createTempFile(name) {
-  createFile(`./temp/${name}`);
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免副作用
-A function produces a side effect if it does anything other than take a value in
-and return another value or values. A side effect could be writing to a file,
-modifying some global variable, or accidentally wiring all your money to a
-stranger.
-
-如果一个函数做了除接受一个值然后返回一个值或多个值之外的任何事情， 它将会产生副作用， 它可能是
-写入一个文件， 修改一个全局变量， 或者意外的把你所有的钱连接到一个陌生人那里。
-
-Now, you do need to have side effects in a program on occasion. Like the previous
-example, you might need to write to a file. What you want to do is to
-centralize where you are doing this. Don't have several functions and classes
-that write to a particular file. Have one service that does it. One and only one.
-
-现在在你的程序中确实偶尔需要副作用， 就像上面的代码， 你也许需要写入到一个文件， 你需要做的是集
-中化你要做的事情， 不要让多个函数或者类写入一个特定的文件， 用一个服务来实现它， 一个并且只有一
-个。
-
-The main point is to avoid common pitfalls like sharing state between objects
-without any structure, using mutable data types that can be written to by anything,
-and not centralizing where your side effects occur. If you can do this, you will
-be happier than the vast majority of other programmers.
-
-重点是避免这些常见的易犯的错误， 比如在对象之间共享状态而不使用任何结构， 使用任何地方都可以写入
-的可变的数据类型， 没有集中化导致副作用。 如果你能做到这些， 那么你将会比其它的码农大军更加幸福。
-
-**不好的：**
-```javascript
-// Global variable referenced by following function.
-// 全局变量被下面的函数引用
-// If we had another function that used this name, now it'd be an array and it
-// could break it.
-// 如果我们有另一个函数使用这个 name ， 现在它应该是一个数组， 这可能会出现错误。
-let name = 'Ryan McDermott';
-
-function splitIntoFirstAndLastName() {
-  name = name.split(' ');
-}
-
-splitIntoFirstAndLastName();
-
-console.log(name); // ['Ryan', 'McDermott'];
-```
-
-**好的：**
-```javascript
-function splitIntoFirstAndLastName(name) {
-  return name.split(' ');
-}
-
-const name = 'Ryan McDermott';
-const newName = splitIntoFirstAndLastName(name);
-
-console.log(name); // 'Ryan McDermott';
-console.log(newName); // ['Ryan', 'McDermott'];
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 不要写入全局函数
-Polluting globals is a bad practice in JavaScript because you could clash with another
-library and the user of your API would be none-the-wiser until they get an
-exception in production. Let's think about an example: what if you wanted to
-extend JavaScript's native Array method to have a `diff` method that could
-show the difference between two arrays? You could write your new function
-to the `Array.prototype`, but it could clash with another library that tried
-to do the same thing. What if that other library was just using `diff` to find
-the difference between the first and last elements of an array? This is why it
-would be much better to just use ES2015/ES6 classes and simply extend the `Array` global.
-
-污染全局在 JavaScript 中是一个不好的做法， 因为你可能会和另外一个类库冲突， 你的 API 的用户
-可能不够聪明， 直到他们得到在生产环境得到一个异常。 让我们来考虑这样一个例子： 假设你要扩展
-JavaScript 的 原生 `Array` ， 添加一个可以显示两个数组的不同之处的 `diff` 方法， 你可以在
-`Array.prototype` 中写一个新的方法， 但是它可能会和尝试做相同事情的其它类库发生冲突。 如果有
-另外一个类库仅仅使用 `diff` 方法来查找数组的第一个元素和最后一个元素之间的不同之处呢？ 这就是
-为什么使用 ES2015/ES6 的类是一个更好的做法的原因， 只要简单的扩展全局的 `Array` 即可。
-
-**不好的：**
-```javascript
-Array.prototype.diff = function diff(comparisonArray) {
-  const hash = new Set(comparisonArray);
-  return this.filter(elem => !hash.has(elem));
-};
-```
-
-**好的：**
-```javascript
-class SuperArray extends Array {
-  diff(comparisonArray) {
-    const hash = new Set(comparisonArray);
-    return this.filter(elem => !hash.has(elem));
-  }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 函数式编程优于指令式编程
-JavaScript isn't a functional language in the way that Haskell is, but it has
-a functional flavor to it. Functional languages are cleaner and easier to test.
-Favor this style of programming when you can.
-
-JavaScript 不是 Haskell 那种方式的函数式语言， 但是它有它的函数式风格。 函数式语言更加简洁
-并且更容易进行测试， 当你可以使用函数式编程风格时请尽情使用。
-
-**不好的：**
-```javascript
-const programmerOutput = [
-  {
-    name: 'Uncle Bobby',
-    linesOfCode: 500
-  }, {
-    name: 'Suzie Q',
-    linesOfCode: 1500
-  }, {
-    name: 'Jimmy Gosling',
-    linesOfCode: 150
-  }, {
-    name: 'Gracie Hopper',
-    linesOfCode: 1000
-  }
-];
-
-let totalOutput = 0;
-
-for (let i = 0; i < programmerOutput.length; i++) {
-  totalOutput += programmerOutput[i].linesOfCode;
-}
-```
-
-**好的：**
-```javascript
-const programmerOutput = [
-  {
-    name: 'Uncle Bobby',
-    linesOfCode: 500
-  }, {
-    name: 'Suzie Q',
-    linesOfCode: 1500
-  }, {
-    name: 'Jimmy Gosling',
-    linesOfCode: 150
-  }, {
-    name: 'Gracie Hopper',
-    linesOfCode: 1000
-  }
-];
-
-const totalOutput = programmerOutput
-  .map((programmer) => programmer.linesOfCode)
-  .reduce((acc, linesOfCode) => acc + linesOfCode, 0);
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 封装条件语句
-
-**不好的：**
-```javascript
-if (fsm.state === 'fetching' && isEmpty(listNode)) {
-  // ...
-}
-```
-
-**好的：**
-```javascript
-function shouldShowSpinner(fsm, listNode) {
-  return fsm.state === 'fetching' && isEmpty(listNode);
-}
-
-if (shouldShowSpinner(fsmInstance, listNodeInstance)) {
-  // ...
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免负面条件
-
-**不好的：**
-```javascript
-function isDOMNodeNotPresent(node) {
-  // ...
-}
-
-if (!isDOMNodeNotPresent(node)) {
-  // ...
-}
-```
-
-**好的：**
-```javascript
-function isDOMNodePresent(node) {
-  // ...
-}
-
-if (isDOMNodePresent(node)) {
-  // ...
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免条件
-This seems like an impossible task. Upon first hearing this, most people say,
-"how am I supposed to do anything without an `if` statement?" The answer is that
-you can use polymorphism to achieve the same task in many cases. The second
-question is usually, "well that's great but why would I want to do that?" The
-answer is a previous clean code concept we learned: a function should only do
-one thing. When you have classes and functions that have `if` statements, you
-are telling your user that your function does more than one thing. Remember,
-just do one thing.
-
-这看起来似乎是一个不可能的任务。 第一次听到这个时， 多数人会说： “没有 `if` 语句还能期望我干
-啥呢”， 答案是多数情况下你可以使用多态来完成同样的任务。 第二个问题通常是 “好了， 那么做很棒，
-但是我为什么想要那样做呢”， 答案是我们学到的上一条代码整洁之道的理念： 一个函数应当只做一件事情。
-当你有使用 `if` 语句的类/函数是， 你在告诉你的用户你的函数做了不止一件事情。 记住： 只做一件
-事情。
-
-**不好的：**
-```javascript
-class Airplane {
-  // ...
-  getCruisingAltitude() {
-    switch (this.type) {
-      case '777':
-        return this.getMaxAltitude() - this.getPassengerCount();
-      case 'Air Force One':
-        return this.getMaxAltitude();
-      case 'Cessna':
-        return this.getMaxAltitude() - this.getFuelExpenditure();
-    }
-  }
-}
-```
-
-**好的：**
-```javascript
-class Airplane {
-  // ...
-}
-
-class Boeing777 extends Airplane {
-  // ...
-  getCruisingAltitude() {
-    return this.getMaxAltitude() - this.getPassengerCount();
-  }
-}
-
-class AirForceOne extends Airplane {
-  // ...
-  getCruisingAltitude() {
-    return this.getMaxAltitude();
-  }
-}
-
-class Cessna extends Airplane {
-  // ...
-  getCruisingAltitude() {
-    return this.getMaxAltitude() - this.getFuelExpenditure();
-  }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免类型检查 (part 1)
-JavaScript is untyped, which means your functions can take any type of argument.
-Sometimes you are bitten by this freedom and it becomes tempting to do
-type-checking in your functions. There are many ways to avoid having to do this.
-The first thing to consider is consistent APIs.
-
-JavaScript 是无类型的， 这意味着你的函数能接受任何类型的参数。 但是有时又会被这种自由咬伤，
-于是又尝试在你的函数中做类型检查。 有很多种方式来避免这个， 第一个要考虑的是一致的 API 。
-
-**不好的：**
-```javascript
-function travelToTexas(vehicle) {
-  if (vehicle instanceof Bicycle) {
-    vehicle.peddle(this.currentLocation, new Location('texas'));
-  } else if (vehicle instanceof Car) {
-    vehicle.drive(this.currentLocation, new Location('texas'));
-  }
-}
-```
-
-**好的：**
-```javascript
-function travelToTexas(vehicle) {
-  vehicle.move(this.currentLocation, new Location('texas'));
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免类型检查 (part 2)
-If you are working with basic primitive values like strings, integers, and arrays,
-and you can't use polymorphism but you still feel the need to type-check,
-you should consider using TypeScript. It is an excellent alternative to normal
-JavaScript, as it provides you with static typing on top of standard JavaScript
-syntax. The problem with manually type-checking normal JavaScript is that
-doing it well requires so much extra verbiage that the faux "type-safety" you get
-doesn't make up for the lost readability. Keep your JavaScript clean, write
-good tests, and have good code reviews. Otherwise, do all of that but with
-TypeScript (which, like I said, is a great alternative!).
-
-如果你使用原始的字符串、 整数和数组， 并且你不能使用多态， 但是你依然感觉到有类型检查的需要，
-你应该考虑使用 TypeScript 。 它是一个常规 JavaScript 的优秀的替代品， 因为它在标准的 JavaScript
-语法之上为你提供静态类型。 对常规 JavaScript 做人工类型检查的问题是需要大量的冗词来仿造类型安
-全而不缺失可读性。 保持你的 JavaScript 简洁， 编写良好的测试， 并有良好的代码审阅， 否则使用
-TypeScript （就像我说的， 它是一个伟大的替代品）来完成这些。
-
-**不好的：**
-```javascript
-function combine(val1, val2) {
-  if (typeof val1 === 'number' && typeof val2 === 'number' ||
-      typeof val1 === 'string' && typeof val2 === 'string') {
-    return val1 + val2;
-  }
-
-  throw new Error('Must be of type String or Number');
-}
-```
-
-**好的：**
-```javascript
-function combine(val1, val2) {
-  return val1 + val2;
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 不要过度优化
-Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
-times, if you are optimizing then you are just wasting your time. [There are good
-resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)
-for seeing where optimization is lacking. Target those in the meantime, until
-they are fixed if they can be.
-
-现代化浏览器运行时在幕后做大量的优化， 在大多数的时间， 做优化就是在浪费你的时间。 [这些是好的
-资源](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)， 用来
-查看那些地方需要优化。 为这些而优化， 直到他们被修正。
-
-**不好的：**
-```javascript
-
-// On old browsers, each iteration with uncached `list.length` would be costly
-// because of `list.length` recomputation. In modern browsers, this is optimized.
-// 在旧的浏览器上， 每次循环 `list.length` 都没有被缓存， 会导致不必要的开销， 因为要重新计
-// 算 `list.length` 。 在现代化浏览器上， 这个已经被优化了。
-for (let i = 0, len = list.length; i < len; i++) {
-  // ...
-}
-```
-
-**好的：**
-```javascript
-for (let i = 0; i < list.length; i++) {
-  // ...
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 移除僵尸代码
-Dead code is just as bad as duplicate code. There's no reason to keep it in
-your codebase. If it's not being called, get rid of it! It will still be safe
-in your version history if you still need it.
-
-僵死代码和冗余代码同样糟糕。 没有理由在代码库中保存它。 如果它不会被调用， 就删掉它。 当你需要
-它时， 它依然保存在版本历史记录中。
-
-**不好的：**
-```javascript
-function oldRequestModule(url) {
-  // ...
-}
-
-function newRequestModule(url) {
-  // ...
-}
-
-const req = newRequestModule;
-inventoryTracker('apples', req, 'www.inventory-awesome.io');
-
-```
-
-**好的：**
-```javascript
-function newRequestModule(url) {
-  // ...
-}
-
-const req = newRequestModule;
-inventoryTracker('apples', req, 'www.inventory-awesome.io');
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **对象和数据结构**
-### 使用 getters 和 setters
-JavaScript doesn't have interfaces or types so it is very hard to enforce this
-pattern, because we don't have keywords like `public` and `private`. As it is,
-using getters and setters to access data on objects is far better than simply
-looking for a property on an object. "Why?" you might ask. Well, here's an
-unorganized list of reasons why:
-
-JavaScript 没有接口或类型， 所以坚持这个模式是非常困难的， 因为我们没有 `public` 和 `private`
-关键字。 正因为如此， 使用 getters 和 setters 来访问对象上的数据比简单的在一个对象上查找属性
-要好得多。 “为什么？” 你可能会问， 好吧， 原因请看下面的列表：
-
-* When you want to do more beyond getting an object property, you don't have
-to look up and change every accessor in your codebase.
-* Makes adding validation simple when doing a `set`.
-* Encapsulates the internal representation.
-* Easy to add logging and error handling when getting and setting.
-* Inheriting this class, you can override default functionality.
-* You can lazy load your object's properties, let's say getting it from a
-server.
-
-* 当你想在获取一个对象属性的背后做更多的事情时， 你不需要在代码库中查找和修改每一处访问；
-* 使用 `set` 可以让添加验证变得容易；
-* 封装内部实现；
-* 使用 getting 和 setting 时， 容易添加日志和错误处理；
-* 继承这个类， 你可以重写默认功能；
-* 你可以延迟加载对象的属性， 比如说从服务器获取。
-
-**不好的：**
-```javascript
-class BankAccount {
-  constructor() {
-    this.balance = 1000;
-  }
-}
-
-const bankAccount = new BankAccount();
-
-// Buy shoes...
-bankAccount.balance -= 100;
-```
-
-**好的：**
-```javascript
-class BankAccount {
-  constructor(balance = 1000) {
-    this._balance = balance;
-  }
-
-  // It doesn't have to be prefixed with `get` or `set` to be a getter/setter
-  set balance(amount) {
-    if (verifyIfAmountCanBeSetted(amount)) {
-      this._balance = amount;
-    }
-  }
-
-  get balance() {
-    return this._balance;
-  }
-
-  verifyIfAmountCanBeSetted(val) {
-    // ...
-  }
-}
-
-const bankAccount = new BankAccount();
-
-// Buy shoes...
-bankAccount.balance -= shoesPrice;
-
-// Get balance
-let balance = bankAccount.balance;
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-### 让对象拥有私有成员
-这个可以通过闭包来实现（针对 ES5 或更低）。
-
-**不好的：**
-```javascript
-
-const Employee = function(name) {
-  this.name = name;
-};
-
-Employee.prototype.getName = function getName() {
-  return this.name;
-};
-
-const employee = new Employee('John Doe');
-console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
-delete employee.name;
-console.log(`Employee name: ${employee.getName()}`); // Employee name: undefined
-```
-
-**好的：**
-```javascript
-const Employee = function (name) {
-  this.getName = function getName() {
-    return name;
-  };
-};
-
-const employee = new Employee('John Doe');
-console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
-delete employee.name;
-console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-## **类**
-### ES2015/ES6 类优先与 ES5 纯函数
-It's very difficult to get readable class inheritance, construction, and method
-definitions for classical ES5 classes. If you need inheritance (and be aware
-that you might not), then prefer classes. However, prefer small functions over
-classes until you find yourself needing larger and more complex objects.
-
-很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
-要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
-对象。
-
-**不好的：**
-```javascript
-const Animal = function(age) {
-  if (!(this instanceof Animal)) {
-    throw new Error('Instantiate Animal with `new`');
-  }
-
-  this.age = age;
-};
-
-Animal.prototype.move = function move() {};
-
-const Mammal = function(age, furColor) {
-  if (!(this instanceof Mammal)) {
-    throw new Error('Instantiate Mammal with `new`');
-  }
-
-  Animal.call(this, age);
-  this.furColor = furColor;
-};
-
-Mammal.prototype = Object.create(Animal.prototype);
-Mammal.prototype.constructor = Mammal;
-Mammal.prototype.liveBirth = function liveBirth() {};
-
-const Human = function(age, furColor, languageSpoken) {
-  if (!(this instanceof Human)) {
-    throw new Error('Instantiate Human with `new`');
-  }
-
-  Mammal.call(this, age, furColor);
-  this.languageSpoken = languageSpoken;
-};
-
-Human.prototype = Object.create(Mammal.prototype);
-Human.prototype.constructor = Human;
-Human.prototype.speak = function speak() {};
-```
-
-**好的**
-```javascript
-class Animal {
-  constructor(age) {
-    this.age = age;
-  }
-
-  move() { /* ... */ }
-}
-
-class Mammal extends Animal {
-  constructor(age, furColor) {
-    super(age);
-    this.furColor = furColor;
-  }
-
-  liveBirth() { /* ... */ }
-}
-
-class Human extends Mammal {
-  constructor(age, furColor, languageSpoken) {
-    super(age, furColor);
-    this.languageSpoken = languageSpoken;
-  }
-
-  speak() { /* ... */ }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 使用方法链
-This pattern is very useful in JavaScript and you see it in many libraries such
-as jQuery and Lodash. It allows your code to be expressive, and less verbose.
-For that reason, I say, use method chaining and take a look at how clean your code
-will be. In your class functions, simply return `this` at the end of every function,
-and you can chain further class methods onto it.
-
-这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
-它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
-会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
-其它方法链在一起。
-
-**不好的：**
-```javascript
-class Car {
-  constructor() {
-    this.make = 'Honda';
-    this.model = 'Accord';
-    this.color = 'white';
-  }
-
-  setMake(make) {
-    this.make = make;
-  }
-
-  setModel(model) {
-    this.model = model;
-  }
-
-  setColor(color) {
-    this.color = color;
-  }
-
-  save() {
-    console.log(this.make, this.model, this.color);
-  }
-}
-
-const car = new Car();
-car.setColor('pink');
-car.setMake('Ford');
-car.setModel('F-150');
-car.save();
-```
-
-**好的：**
-```javascript
-class Car {
-  constructor() {
-    this.make = 'Honda';
-    this.model = 'Accord';
-    this.color = 'white';
-  }
-
-  setMake(make) {
-    this.make = make;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  setModel(model) {
-    this.model = model;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  setColor(color) {
-    this.color = color;
-    // NOTE: Returning this for chaining
-    return this;
-  }
-
-  save() {
-    console.log(this.make, this.model, this.color);
-    // NOTE: Returning this for chaining
-    return this;
-  }
-}
-
-const car = new Car()
-  .setColor('pink')
-  .setMake('Ford')
-  .setModel('F-150')
-  .save();
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 组合优先于继承
-As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
-you should prefer composition over inheritance where you can. There are lots of
-good reasons to use inheritance and lots of good reasons to use composition.
-The main point for this maxim is that if your mind instinctively goes for
-inheritance, try to think if composition could model your problem better. In some
-cases it can.
-
-正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
-你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
-的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
-可以。
-
-You might be wondering then, "when should I use inheritance?" It
-depends on your problem at hand, but this is a decent list of when inheritance
-makes more sense than composition:
-
-那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
-明什么时候继承比组合更好用：
-
-1. Your inheritance represents an "is-a" relationship and not a "has-a"
-relationship (Human->Animal vs. User->UserDetails).
-2. You can reuse code from the base classes (Humans can move like all animals).
-3. You want to make global changes to derived classes by changing a base class.
-(Change the caloric expenditure of all animals when they move).
-
-
-1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
-2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
-3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
-
-**不好的：**
-```javascript
-class Employee {
-  constructor(name, email) {
-    this.name = name;
-    this.email = email;
-  }
-
-  // ...
-}
-
-// Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
-// 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
-class EmployeeTaxData extends Employee {
-  constructor(ssn, salary) {
-    super();
-    this.ssn = ssn;
-    this.salary = salary;
-  }
-
-  // ...
-}
-```
-
-**好的：**
-```javascript
-class EmployeeTaxData {
-  constructor(ssn, salary) {
-    this.ssn = ssn;
-    this.salary = salary;
-  }
-
-  // ...
-}
-
-class Employee {
-  constructor(name, email) {
-    this.name = name;
-    this.email = email;
-  }
-
-  setTaxData(ssn, salary) {
-    this.taxData = new EmployeeTaxData(ssn, salary);
-  }
-  // ...
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **SOLID**
-### 单一职责原则 (SRP)
-As stated in Clean Code, "There should never be more than one reason for a class
-to change". It's tempting to jam-pack a class with a lot of functionality, like
-when you can only take one suitcase on your flight. The issue with this is
-that your class won't be conceptually cohesive and it will give it many reasons
-to change. Minimizing the amount of times you need to change a class is important.
-It's important because if too much functionality is in one class and you modify a piece of it,
-it can be difficult to understand how that will affect other dependent modules in
-your codebase.
-
-正如代码整洁之道所述， “永远不要有超过一个理由来修改一个类”。 给一个类塞满许多功能， 就像你在航
-班上只能带一个行李箱一样， 这样做的问题你的类不会有理想的内聚性， 将会有太多的理由来对它进行修改。
-最小化需要修改一个类的次数时很重要的， 因为如果一个类拥有太多的功能， 一旦你修改它的一小部分，
-将会很难弄清楚会对代码库中的其它模块造成什么影响。
-
-**好的：**
-```javascript
-class UserSettings {
-  constructor(user) {
-    this.user = user;
-  }
-
-  changeSettings(settings) {
-    if (this.verifyCredentials()) {
-      // ...
-    }
-  }
-
-  verifyCredentials() {
-    // ...
-  }
-}
-```
-
-**好的：**
-```javascript
-class UserAuth {
-  constructor(user) {
-    this.user = user;
-  }
-
-  verifyCredentials() {
-    // ...
-  }
-}
-
-
-class UserSettings {
-  constructor(user) {
-    this.user = user;
-    this.auth = new UserAuth(user);
-  }
-
-  changeSettings(settings) {
-    if (this.auth.verifyCredentials()) {
-      // ...
-    }
-  }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 开闭原则 (OCP)
-As stated by Bertrand Meyer, "software entities (classes, modules, functions,
-etc.) should be open for extension, but closed for modification." What does that
-mean though? This principle basically states that you should allow users to
-add new functionalities without changing existing code.
-
-Bertrand Meyer 说过， “软件实体 (类， 模块， 函数等) 应该为扩展开放， 但是为修改关闭。” 这
-是什么意思呢？ 这个原则基本上说明了你应该允许用户添加功能而不必修改现有的代码。
-
-**不好的：**
-```javascript
-class AjaxAdapter extends Adapter {
-  constructor() {
-    super();
-    this.name = 'ajaxAdapter';
-  }
-}
-
-class NodeAdapter extends Adapter {
-  constructor() {
-    super();
-    this.name = 'nodeAdapter';
-  }
-}
-
-class HttpRequester {
-  constructor(adapter) {
-    this.adapter = adapter;
-  }
-
-  fetch(url) {
-    if (this.adapter.name === 'ajaxAdapter') {
-      return makeAjaxCall(url).then((response) => {
-        // transform response and return
-      });
-    } else if (this.adapter.name === 'httpNodeAdapter') {
-      return makeHttpCall(url).then((response) => {
-        // transform response and return
-      });
-    }
-  }
-}
-
-function makeAjaxCall(url) {
-  // request and return promise
-}
-
-function makeHttpCall(url) {
-  // request and return promise
-}
-```
-
-**好的：**
-```javascript
-class AjaxAdapter extends Adapter {
-  constructor() {
-    super();
-    this.name = 'ajaxAdapter';
-  }
-
-  request(url) {
-    // request and return promise
-  }
-}
-
-class NodeAdapter extends Adapter {
-  constructor() {
-    super();
-    this.name = 'nodeAdapter';
-  }
-
-  request(url) {
-    // request and return promise
-  }
-}
-
-class HttpRequester {
-  constructor(adapter) {
-    this.adapter = adapter;
-  }
-
-  fetch(url) {
-    return this.adapter.request(url).then((response) => {
-      // transform response and return
-    });
-  }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 里氏代换原则 (LSP)
-This is a scary term for a very simple concept. It's formally defined as "If S
-is a subtype of T, then objects of type T may be replaced with objects of type S
-(i.e., objects of type S may substitute objects of type T) without altering any
-of the desirable properties of that program (correctness, task performed,
-etc.)." That's an even scarier definition.
-
-这是针对一个非常简单的里面的一个恐怖意图， 它的正式定义是： “如果 S 是 T 的一个子类型， 那么类
-型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）儿不需
-要修改目标程序的期望性质 （正确性、 任务执行性等）。” 这甚至是个恐怖的定义。
-
-The best explanation for this is if you have a parent class and a child class,
-then the base class and child class can be used interchangeably without getting
-incorrect results. This might still be confusing, so let's take a look at the
-classic Square-Rectangle example. Mathematically, a square is a rectangle, but
-if you model it using the "is-a" relationship via inheritance, you quickly
-get into trouble.
-
-最好的解释是， 如果你又一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
-能还有有些疑惑， 让我们来看一下这个经典的正方形与矩形的例子。 从数学上说， 一个正方形是一个矩形，
-但是你用 "is-a" 的关系用继承来实现， 你将很快遇到麻烦。
-
-**不好的：**
-```javascript
-class Rectangle {
-  constructor() {
-    this.width = 0;
-    this.height = 0;
-  }
-
-  setColor(color) {
-    // ...
-  }
-
-  render(area) {
-    // ...
-  }
-
-  setWidth(width) {
-    this.width = width;
-  }
-
-  setHeight(height) {
-    this.height = height;
-  }
-
-  getArea() {
-    return this.width * this.height;
-  }
-}
-
-class Square extends Rectangle {
-  setWidth(width) {
-    this.width = width;
-    this.height = width;
-  }
-
-  setHeight(height) {
-    this.width = height;
-    this.height = height;
-  }
-}
-
-function renderLargeRectangles(rectangles) {
-  rectangles.forEach((rectangle) => {
-    rectangle.setWidth(4);
-    rectangle.setHeight(5);
-    const area = rectangle.getArea(); // BAD: Will return 25 for Square. Should be 20.
-    rectangle.render(area);
-  });
-}
-
-const rectangles = [new Rectangle(), new Rectangle(), new Square()];
-renderLargeRectangles(rectangles);
-```
-
-**好的：**
-```javascript
-class Shape {
-  setColor(color) {
-    // ...
-  }
-
-  render(area) {
-    // ...
-  }
-}
-
-class Rectangle extends Shape {
-  constructor(width, height) {
-    super();
-    this.width = width;
-    this.height = height;
-  }
-
-  getArea() {
-    return this.width * this.height;
-  }
-}
-
-class Square extends Shape {
-  constructor(length) {
-    super();
-    this.length = length;
-  }
-
-  getArea() {
-    return this.length * this.length;
-  }
-}
-
-function renderLargeShapes(shapes) {
-  shapes.forEach((shape) => {
-    const area = shape.getArea();
-    shape.render(area);
-  });
-}
-
-const shapes = [new Rectangle(4, 5), new Rectangle(4, 5), new Square(5)];
-renderLargeShapes(shapes);
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 接口隔离原则 (ISP)
-JavaScript doesn't have interfaces so this principle doesn't apply as strictly
-as others. However, it's important and relevant even with JavaScript's lack of
-type system.
-
-JavaScript 没有接口， 所以这个原则不想其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
-型的语言来说， 它依然是重要并且有意义的。
-
-ISP states that "Clients should not be forced to depend upon interfaces that
-they do not use." Interfaces are implicit contracts in JavaScript because of
-duck typing.
-
-接口隔离原则说的是 “客户端不应该强制依赖他们不需要的接口。” 在 JavaScript 这种弱类型语言中，
-接口是隐式的契约。
-
-A good example to look at that demonstrates this principle in JavaScript is for
-classes that require large settings objects. Not requiring clients to setup
-huge amounts of options is beneficial, because most of the time they won't need
-all of the settings. Making them optional helps prevent having a "fat interface".
-
-在 JavaScript 中能比较好的说明这个原则的是一个类需要一个巨大的配置对象。 不需要客户端去设置大
-量的选项是有益的， 因为多数情况下他们不需要全部的设置。 让它们变成可选的有助于防止出现一个“胖接
-口”。
-
-**不好的：**
-```javascript
-class DOMTraverser {
-  constructor(settings) {
-    this.settings = settings;
-    this.setup();
-  }
-
-  setup() {
-    this.rootNode = this.settings.rootNode;
-    this.animationModule.setup();
-  }
-
-  traverse() {
-    // ...
-  }
-}
-
-const $ = new DOMTraverser({
-  rootNode: document.getElementsByTagName('body'),
-  animationModule() {} // Most of the time, we won't need to animate when traversing.
-  // ...
-});
-
-```
-
-**好的：**
-```javascript
-class DOMTraverser {
-  constructor(settings) {
-    this.settings = settings;
-    this.options = settings.options;
-    this.setup();
-  }
-
-  setup() {
-    this.rootNode = this.settings.rootNode;
-    this.setupOptions();
-  }
-
-  setupOptions() {
-    if (this.options.animationModule) {
-      // ...
-    }
-  }
-
-  traverse() {
-    // ...
-  }
-}
-
-const $ = new DOMTraverser({
-  rootNode: document.getElementsByTagName('body'),
-  options: {
-    animationModule() {}
-  }
-});
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 依赖反转原则 (DIP)
-This principle states two essential things:
-1. High-level modules should not depend on low-level modules. Both should
-depend on abstractions.
-2. Abstractions should not depend upon details. Details should depend on
-abstractions.
-
-这个原则阐述了两个重要的事情：
-1. 高级模块不应该依赖于低级模块， 两者都应该依赖与抽象；
-2. 抽象不应当依赖于具体实现， 具体实现应当依赖于抽象。
-
-This can be hard to understand at first, but if you've worked with Angular.js,
-you've seen an implementation of this principle in the form of Dependency
-Injection (DI). While they are not identical concepts, DIP keeps high-level
-modules from knowing the details of its low-level modules and setting them up.
-It can accomplish this through DI. A huge benefit of this is that it reduces
-the coupling between modules. Coupling is a very bad development pattern because
-it makes your code hard to refactor.
-
-这个一开始会很难理解， 但是如果你使用过 Angular.js ， 你应该已经看到过通过依赖注入来实现的这
-个原则， 虽然他们不是相同的概念， 依赖反转原则让高级模块远离低级模块的细节和创建， 可以通过 DI
-来实现。 这样做的巨大益处是降低模块间的耦合。 耦合是一个非常糟糕的开发模式， 因为会导致代码难于
-重构。
-
-As stated previously, JavaScript doesn't have interfaces so the abstractions
-that are depended upon are implicit contracts. That is to say, the methods
-and properties that an object/class exposes to another object/class. In the
-example below, the implicit contract is that any Request module for an
-`InventoryTracker` will have a `requestItems` method.
-
-如上所述， JavaScript 没有接口， 所以被依赖的抽象是隐式契约。 也就是说， 一个对象/类的方法和
-属性直接暴露给另外一个对象/类。 在下面的例子中， 任何一个 Request 模块的隐式契约 `InventoryTracker`
-将有一个 `requestItems` 方法。
-
-**不好的：**
-```javascript
-class InventoryRequester {
-  constructor() {
-    this.REQ_METHODS = ['HTTP'];
-  }
-
-  requestItem(item) {
-    // ...
-  }
-}
-
-class InventoryTracker {
-  constructor(items) {
-    this.items = items;
-
-    // BAD: We have created a dependency on a specific request implementation.
-    // We should just have requestItems depend on a request method: `request`
-    // 不好的： 我们已经创建了一个对请求的具体实现的依赖， 我们只有一个 requestItems 方法依
-    // 赖一个请求方法 'request'
-    this.requester = new InventoryRequester();
-  }
-
-  requestItems() {
-    this.items.forEach((item) => {
-      this.requester.requestItem(item);
-    });
-  }
-}
-
-const inventoryTracker = new InventoryTracker(['apples', 'bananas']);
-inventoryTracker.requestItems();
-```
-
-**好的：**
-```javascript
-class InventoryTracker {
-  constructor(items, requester) {
-    this.items = items;
-    this.requester = requester;
-  }
-
-  requestItems() {
-    this.items.forEach((item) => {
-      this.requester.requestItem(item);
-    });
-  }
-}
-
-class InventoryRequesterV1 {
-  constructor() {
-    this.REQ_METHODS = ['HTTP'];
-  }
-
-  requestItem(item) {
-    // ...
-  }
-}
-
-class InventoryRequesterV2 {
-  constructor() {
-    this.REQ_METHODS = ['WS'];
-  }
-
-  requestItem(item) {
-    // ...
-  }
-}
-
-// By constructing our dependencies externally and injecting them, we can easily
-// substitute our request module for a fancy new one that uses WebSockets.
-// 通过外部创建依赖项并将它们注入， 我们可以轻松的用一个崭新的使用 WebSockets 的请求模块进行
-// 替换。
-const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
-inventoryTracker.requestItems();
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **测试**
-Testing is more important than shipping. If you have no tests or an
-inadequate amount, then every time you ship code you won't be sure that you
-didn't break anything. Deciding on what constitutes an adequate amount is up
-to your team, but having 100% coverage (all statements and branches) is how
-you achieve very high confidence and developer peace of mind. This means that
-in addition to having a great testing framework, you also need to use a
-[good coverage tool](http://gotwarlost.github.io/istanbul/).
-
-测试比发布更加重要。 如果你没有测试或者测试不够充分， 每次发布时你就不能确认没有破坏任何事情。
-测试的量由你的团队决定， 但是拥有 100% 的覆盖率(包括所有的语句和分支)是你为什么能达到高度自信
-和内心的平静。 这意味着需要一个额外的伟大的测试框架， 也需要一个好的[覆盖率工具](http://gotwarlost.github.io/istanbul/)。
-
-There's no excuse to not write tests. There's [plenty of good JS test frameworks]
-(http://jstherightway.org/#testing-tools), so find one that your team prefers.
-When you find one that works for your team, then aim to always write tests
-for every new feature/module you introduce. If your preferred method is
-Test Driven Development (TDD), that is great, but the main point is to just
-make sure you are reaching your coverage goals before launching any feature,
-or refactoring an existing one.
-
-没有理由不写测试。 这里有[大量的优秀的 JS 测试框架](http://jstherightway.org/#testing-tools)，
-选一个适合你的团队的即可。 当为团队选择了测试框架之后， 接下来的目标是为生产的每一个新的功能／模
-块编写测试。 如果你倾向于测试驱动开发(TDD)， 那就太棒了， 但是要点是确认你在上线任何功能或者重
-构一个现有功能之前， 达到了需要的目标覆盖率。
-
-### 一个测试一个概念
-
-**不好的：**
-```javascript
-const assert = require('assert');
-
-describe('MakeMomentJSGreatAgain', () => {
-  it('handles date boundaries', () => {
-    let date;
-
-    date = new MakeMomentJSGreatAgain('1/1/2015');
-    date.addDays(30);
-    date.shouldEqual('1/31/2015');
-
-    date = new MakeMomentJSGreatAgain('2/1/2016');
-    date.addDays(28);
-    assert.equal('02/29/2016', date);
-
-    date = new MakeMomentJSGreatAgain('2/1/2015');
-    date.addDays(28);
-    assert.equal('03/01/2015', date);
-  });
-});
-```
-
-**好的：**
-```javascript
-const assert = require('assert');
-
-describe('MakeMomentJSGreatAgain', () => {
-  it('handles 30-day months', () => {
-    const date = new MakeMomentJSGreatAgain('1/1/2015');
-    date.addDays(30);
-    date.shouldEqual('1/31/2015');
-  });
-
-  it('handles leap year', () => {
-    const date = new MakeMomentJSGreatAgain('2/1/2016');
-    date.addDays(28);
-    assert.equal('02/29/2016', date);
-  });
-
-  it('handles non-leap year', () => {
-    const date = new MakeMomentJSGreatAgain('2/1/2015');
-    date.addDays(28);
-    assert.equal('03/01/2015', date);
-  });
-});
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **并发**
-### 使用 Promises, 不要使用回调
-Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
-Promises are a built-in global type. Use them!
-
-回调不够简洁， 因为他们会产生过多的嵌套。 在 ES2015/ES6 中， Promises 已经是内置的全局类型
-了，使用它们吧！
-
-**不好的：**
-```javascript
-require('request').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response) => {
-  if (requestErr) {
-    console.error(requestErr);
-  } else {
-    require('fs').writeFile('article.html', response.body, (writeErr) => {
-      if (writeErr) {
-        console.error(writeErr);
-      } else {
-        console.log('File written');
-      }
-    });
-  }
-});
-
-```
-
-**好的：**
-```javascript
-require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
-  .then((response) => {
-    return require('fs-promise').writeFile('article.html', response);
-  })
-  .then(() => {
-    console.log('File written');
-  })
-  .catch((err) => {
-    console.error(err);
-  });
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### Async/Await 比 Promises 更加简洁
-Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
-which offer an even cleaner solution. All you need is a function that is prefixed
-in an `async` keyword, and then you can write your logic imperatively without
-a `then` chain of functions. Use this if you can take advantage of ES2017/ES8 features
-today!
-
-Promises 是回调的一个非常简洁的替代品， 但是 ES2017/ES8 带来的 async 和 await 提供了一个
-更加简洁的解决方案。 你需要的只是一个前缀为 `async` 关键字的函数， 接下来就可以不需要 `then`
-函数链来编写逻辑了。 如果你能使用 ES2017/ES8 的高级功能的话， 今天就使用它吧！
-
-**不好的：**
-```javascript
-require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
-  .then((response) => {
-    return require('fs-promise').writeFile('article.html', response);
-  })
-  .then(() => {
-    console.log('File written');
-  })
-  .catch((err) => {
-    console.error(err);
-  });
-
-```
-
-**好的：**
-```javascript
-async function getCleanCodeArticle() {
-  try {
-    const response = await require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin');
-    await require('fs-promise').writeFile('article.html', response);
-    console.log('File written');
-  } catch(err) {
-    console.error(err);
-  }
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-## **错误处理**
-Thrown errors are a good thing! They mean the runtime has successfully
-identified when something in your program has gone wrong and it's letting
-you know by stopping function execution on the current stack, killing the
-process (in Node), and notifying you in the console with a stack trace.
-
-抛出错误是一件好事情！ 他们意味着当你的程序有错时运行时可以成功确认， 并且通过停止执行当前堆栈
-上的函数来让你知道， 结束当前进程（在 Node 中）， 在控制台中用一个堆栈跟踪提示你。
-
-### 不要忽略捕捉到的错误
-Doing nothing with a caught error doesn't give you the ability to ever fix
-or react to said error. Logging the error to the console (`console.log`)
-isn't much better as often times it can get lost in a sea of things printed
-to the console. If you wrap any bit of code in a `try/catch` it means you
-think an error may occur there and therefore you should have a plan,
-or create a code path, for when it occurs.
-
-对捕捉到的错误不做任何处理不能给你修复错误或者响应错误的能力。 向控制台记录错误 (`console.log`)
-也不怎么好， 因为往往会丢失在海量的控制台输出中。 如果你把任意一段代码用 `try/catch` 包装那就
-意味着你想到这里可能会错， 因此你应该有个修复计划， 或者当错误发生时有一个代码路径。
-
-**不好的：**
-```javascript
-try {
-  functionThatMightThrow();
-} catch (error) {
-  console.log(error);
-}
-```
-
-**好的：**
-```javascript
-try {
-  functionThatMightThrow();
-} catch (error) {
-  // One option (more noisy than console.log):
-  console.error(error);
-  // Another option:
-  notifyUserOfError(error);
-  // Another option:
-  reportErrorToService(error);
-  // OR do all three!
-}
-```
-
-### 不要忽略被拒绝的 promise 
-For the same reason you shouldn't ignore caught errors
-from `try/catch`.
-
-与你不应忽略来自 `try/catch` 的错误的原因相同。
-
-**不好的：**
-```javascript
-getdata()
-.then((data) => {
-  functionThatMightThrow(data);
-})
-.catch((error) => {
-  console.log(error);
-});
-```
-
-**好的：**
-```javascript
-getdata()
-.then((data) => {
-  functionThatMightThrow(data);
-})
-.catch((error) => {
-  // One option (more noisy than console.log):
-  console.error(error);
-  // Another option:
-  notifyUserOfError(error);
-  // Another option:
-  reportErrorToService(error);
-  // OR do all three!
-});
-```
-
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-## **格式化**
-Formatting is subjective. Like many rules herein, there is no hard and fast
-rule that you must follow. The main point is DO NOT ARGUE over formatting.
-There are [tons of tools](http://standardjs.com/rules.html) to automate this.
-Use one! It's a waste of time and money for engineers to argue over formatting.
-
-格式化是主观的。 就像其它规则一样， 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论， 这
-里有[大量的工具](http://standardjs.com/rules.html)来自动格式化， 使用其中的一个即可！ 因
-为做为工程师去争论格式化就是在浪费时间和金钱。
-
-For things that don't fall under the purview of automatic formatting
-(indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
-for some guidance.
-
-针对自动格式化工具不能涵盖的问题（缩进、 制表符还是空格、 双引号还是单引号等）， 这里有一些指南。
-
-### 使用一致的大小写
-JavaScript is untyped, so capitalization tells you a lot about your variables,
-functions, etc. These rules are subjective, so your team can choose whatever
-they want. The point is, no matter what you all choose, just be consistent.
-
-JavaScript 是无类型的， 所以大小写告诉你关于你的变量、 函数等的很多事情。 这些规则是主观的，
-所以你的团队可以选择他们想要的。 重点是， 不管你们选择了什么， 要保持一致。
-
-**不好的：**
-```javascript
-const DAYS_IN_WEEK = 7;
-const daysInMonth = 30;
-
-const songs = ['Back In Black', 'Stairway to Heaven', 'Hey Jude'];
-const Artists = ['ACDC', 'Led Zeppelin', 'The Beatles'];
-
-function eraseDatabase() {}
-function restore_database() {}
-
-class animal {}
-class Alpaca {}
-```
-
-**好的：**
-```javascript
-const DAYS_IN_WEEK = 7;
-const DAYS_IN_MONTH = 30;
-
-const songs = ['Back In Black', 'Stairway to Heaven', 'Hey Jude'];
-const artists = ['ACDC', 'Led Zeppelin', 'The Beatles'];
-
-function eraseDatabase() {}
-function restoreDatabase() {}
-
-class Animal {}
-class Alpaca {}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-
-### 函数的调用方与被调用方应该靠近
-If a function calls another, keep those functions vertically close in the source
-file. Ideally, keep the caller right above the callee. We tend to read code from
-top-to-bottom, like a newspaper. Because of this, make your code read that way.
-
-如果一个函数调用另一个， 则在代码中这两个函数的竖直位置应该靠近。 理想情况下，保持被调用函数在被
-调用函数的正上方。 我们倾向于从上到下阅读代码， 就像读一章报纸。 由于这个原因， 保持你的代码可
-以按照这种方式阅读。
-
-**不好的：**
-```javascript
-class PerformanceReview {
-  constructor(employee) {
-    this.employee = employee;
-  }
-
-  lookupPeers() {
-    return db.lookup(this.employee, 'peers');
-  }
-
-  lookupManager() {
-    return db.lookup(this.employee, 'manager');
-  }
-
-  getPeerReviews() {
-    const peers = this.lookupPeers();
-    // ...
-  }
-
-  perfReview() {
-    this.getPeerReviews();
-    this.getManagerReview();
-    this.getSelfReview();
-  }
-
-  getManagerReview() {
-    const manager = this.lookupManager();
-  }
-
-  getSelfReview() {
-    // ...
-  }
-}
-
-const review = new PerformanceReview(user);
-review.perfReview();
-```
-
-**好的：**
-```javascript
-class PerformanceReview {
-  constructor(employee) {
-    this.employee = employee;
-  }
-
-  perfReview() {
-    this.getPeerReviews();
-    this.getManagerReview();
-    this.getSelfReview();
-  }
-
-  getPeerReviews() {
-    const peers = this.lookupPeers();
-    // ...
-  }
-
-  lookupPeers() {
-    return db.lookup(this.employee, 'peers');
-  }
-
-  getManagerReview() {
-    const manager = this.lookupManager();
-  }
-
-  lookupManager() {
-    return db.lookup(this.employee, 'manager');
-  }
-
-  getSelfReview() {
-    // ...
-  }
-}
-
-const review = new PerformanceReview(employee);
-review.perfReview();
-```
-
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## **评论**
-### 仅仅对包含复杂业务逻辑的东西进行评论
-Comments are an apology, not a requirement. Good code *mostly* documents itself.
-
-评论是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
-
-**不好的：**
-```javascript
-function hashIt(data) {
-  // The hash
-  let hash = 0;
-
-  // Length of string
-  const length = data.length;
-
-  // Loop through every character in data
-  for (let i = 0; i < length; i++) {
-    // Get character code.
-    const char = data.charCodeAt(i);
-    // Make the hash
-    hash = ((hash << 5) - hash) + char;
-    // Convert to 32-bit integer
-    hash &= hash;
-  }
-}
-```
-
-**好的：**
-```javascript
-
-function hashIt(data) {
-  let hash = 0;
-  const length = data.length;
-
-  for (let i = 0; i < length; i++) {
-    const char = data.charCodeAt(i);
-    hash = ((hash << 5) - hash) + char;
-
-    // Convert to 32-bit integer
-    hash &= hash;
-  }
-}
-
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 不要在代码库中保存注释掉的代码
-Version control exists for a reason. Leave old code in your history.
-
-因为有版本控制， 把旧的代码留在历史记录即可。
-
-**不好的：**
-```javascript
-doStuff();
-// doOtherStuff();
-// doSomeMoreStuff();
-// doSoMuchStuff();
-```
-
-**好的：**
-```javascript
-doStuff();
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 不要有日志式的评论
-Remember, use version control! There's no need for dead code, commented code,
-and especially journal comments. Use `git log` to get history!
-
-记住， 使用版本控制！ 不需要僵尸代码， 注释调的代码， 尤其是日志式的评论。 使用 `git log` 来
-获取历史记录。
-
-**不好的：**
-```javascript
-/**
- * 2016-12-20: Removed monads, didn't understand them (RM)
- * 2016-10-01: Improved using special monads (JP)
- * 2016-02-03: Removed type-checking (LI)
- * 2015-03-14: Added combine with type-checking (JR)
- */
-function combine(a, b) {
-  return a + b;
-}
-```
-
-**好的：**
-```javascript
-function combine(a, b) {
-  return a + b;
-}
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-### 避免占位符
-They usually just add noise. Let the functions and variable names along with the
-proper indentation and formatting give the visual structure to your code.
-
-它们仅仅添加了干扰。 让函数和变量名称与合适的缩进和格式化为你的代码提供视觉结构。
-
-**不好的：**
-```javascript
-////////////////////////////////////////////////////////////////////////////////
-// Scope Model Instantiation
-////////////////////////////////////////////////////////////////////////////////
-$scope.model = {
-  menu: 'foo',
-  nav: 'bar'
-};
-
-////////////////////////////////////////////////////////////////////////////////
-// Action setup
-////////////////////////////////////////////////////////////////////////////////
-const actions = function() {
-  // ...
-};
-```
-
-**好的：**
-```javascript
-$scope.model = {
-  menu: 'foo',
-  nav: 'bar'
-};
-
-const actions = function() {
-  // ...
-};
-```
-**[⬆ 返回顶部](#代码整洁的-javascript)**
-
-## Translation
-
-This is also available in other languages:
-
-  - ![br](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png) **Brazilian Portuguese**: [fesnt/clean-code-javascript](https://github.com/fesnt/clean-code-javascript)
-  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese**:
-    - [alivebao/clean-code-js](https://github.com/alivebao/clean-code-js)
-    - [beginor/clean-code-js](https://github.com/beginor/clean-code-javascript/blob/master/README-zh-CN.md)
-  - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [marcbruederlin/clean-code-javascript](https://github.com/marcbruederlin/clean-code-javascript)
-  - ![kr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png) **Korean**: [qkraudghgh/clean-code-javascript-ko](https://github.com/qkraudghgh/clean-code-javascript-ko)
-  - ![ru](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png) **Russian**:
-    - [BoryaMogila/clean-code-javascript-ru/](https://github.com/BoryaMogila/clean-code-javascript-ru/)
-    - [maksugr/clean-code-javascript](https://github.com/maksugr/clean-code-javascript)
-  - ![vi](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png) **Vietnamese**: [hienvd/clean-code-javascript/](https://github.com/hienvd/clean-code-javascript/)
-
-**[⬆ 返回顶部](#代码整洁的-javascript)**

From 08ef8c859ec811e7f626bcb85b83dbcff5960cbe Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Wed, 15 Feb 2017 13:57:53 +0800
Subject: [PATCH 48/54] add chinese translation, review in progress.

---
 README.md | 908 ++++++++++++++++++++++++++++++++----------------------
 1 file changed, 533 insertions(+), 375 deletions(-)

diff --git a/README.md b/README.md
index ca7d367e..17090f51 100644
--- a/README.md
+++ b/README.md
@@ -1,40 +1,49 @@
-
-# clean-code-javascript
-
-## Table of Contents
-  1. [Introduction](#introduction)
-  2. [Variables](#variables)
-  3. [Functions](#functions)
-  4. [Objects and Data Structures](#objects-and-data-structures)
-  5. [Classes](#classes)
+# 代码整洁的 JavaScript
+
+## 目录
+  1. [简介](#简介)
+  2. [变量](#变量)
+  3. [函数](#函数)
+  4. [对象和数据结构](#对象和数据结构)
+  5. [类](#类)
   6. [SOLID](#solid)
-  7. [Testing](#testing)
-  8. [Concurrency](#concurrency)
-  9. [Error Handling](#error-handling)
-  10. [Formatting](#formatting)
-  11. [Comments](#comments)
+  7. [测试](#测试)
+  8. [并发](#并发)
+  9. [错误处理](#错误处理)
+  10. [格式化](#格式化)
+  11. [评论](#评论)
   12. [Translation](#translation)
 
-## 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)
+## 简介
+![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](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.
 
+将源自 Robert C. Martin 的 [*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
+的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个用 JavaScript 来生产可
+读的， 可重用的， 以及可重构的软件的指南。
+
 Not every principle herein has to be strictly followed, and even fewer 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*.
 
+这里的每一项原则都不是必须遵守的， 甚至只有更少的能够被广泛认可。 这些仅仅是指南而已， 但是却是
+*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.
 
+我们的软件工程行业只有短短的 50 年， 依然有很多要我们去学习。 当软件架构与建筑架构一样古老时，
+也许我们将会有硬性的规则去遵守。 而现在， 让这些指南做为你和你的团队生产的 JavaScript 代码的
+质量的标准。
+
 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
@@ -42,36 +51,42 @@ 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
+还有一件事： 知道这些指南并不能马上让你成为一个更加出色的软件开发者， 并且使用它们工作多年也并
+不意味着你不会犯错误。 每一段代码最开始都是草稿， 像湿粘土一样被打造成最终的形态。 最后当我们
+和搭档们一起审查代码时清除那些不完善之处。 不要因为最初需要改善的草稿代码而自责， 而是对那些代
+码下手。
+
+## **变量**
+### 使用有意义并且可读的变量名称
 
-**Bad:**
+**不好的：**
 ```javascript
 const yyyymmdstr = moment().format('YYYY/MM/DD');
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const currentDate = moment().format('YYYY/MM/DD');
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use the same vocabulary for the same type of variable
+### 为相同类型的变量使用相同的词汇
 
-**Bad:**
+**不好的：**
 ```javascript
 getUserInfo();
 getClientData();
 getCustomerRecord();
 ```
 
-**Good:**
+**好的：**
 ```javascript
 getUser();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+### 使用可搜索的名称
 
-### Use searchable names
 We will read more code than we will ever write. It's important that the code we
 do write is readable and searchable. By *not* naming variables that end up
 being meaningful for understanding our program, we hurt our readers.
@@ -80,44 +95,49 @@ Make your names searchable. Tools like
 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
 can help identify unnamed constants.
 
-**Bad:**
+我们要阅读的代码比要写的代码多得多， 所以我们写出的代码的可读性和可搜索性是很重要的。 使用没有
+意义的变量名将会导致我们的程序难于理解， 将会伤害我们的读者， 所以请使用可搜索的变量名。 类似
+[buddy.js](https://github.com/danielstjules/buddy.js) 和 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
+的工具可以帮助我们找到未命名的常量。
+
+**不好的：**
 ```javascript
-// What the heck is 86400000 for?
+// 艹， 86400000 是什么鬼？
 setTimeout(blastOff, 86400000);
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
-// Declare them as capitalized `const` globals.
+// 将它们声明为全局常量 `const` 。
 const MILLISECONDS_IN_A_DAY = 86400000;
 
 setTimeout(blastOff, MILLISECONDS_IN_A_DAY);
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use explanatory variables
-**Bad:**
+### 使用解释性的变量
+**不好的：**
 ```javascript
 const address = 'One Infinite Loop, Cupertino 95014';
 const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
 saveCityZipCode(address.match(cityZipCodeRegex)[1], address.match(cityZipCodeRegex)[2]);
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const address = 'One Infinite Loop, Cupertino 95014';
 const cityZipCodeRegex = /^[^,\\]+[,\\\s]+(.+?)\s*(\d{5})?$/;
 const [, city, zipCode] = address.match(cityZipCodeRegex) || [];
 saveCityZipCode(city, zipCode);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid Mental Mapping
-Explicit is better than implicit.
+### 避免心理映射
+显示比隐式更好
 
-**Bad:**
+**不好的：**
 ```javascript
 const locations = ['Austin', 'New York', 'San Francisco'];
 locations.forEach((l) => {
@@ -126,12 +146,12 @@ locations.forEach((l) => {
   // ...
   // ...
   // ...
-  // Wait, what is `l` for again?
+  // 等等， `l` 是啥？
   dispatch(l);
 });
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const locations = ['Austin', 'New York', 'San Francisco'];
 locations.forEach((location) => {
@@ -143,13 +163,15 @@ locations.forEach((location) => {
   dispatch(location);
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't add unneeded context
+### 不添加不必要的上下文
 If your class/object name tells you something, don't repeat that in your
 variable name.
 
-**Bad:**
+如果你的类名/对象名有意义， 不要在变量名上再重复。
+
+**不好的：**
 ```javascript
 const Car = {
   carMake: 'Honda',
@@ -162,7 +184,7 @@ function paintCar(car) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const Car = {
   make: 'Honda',
@@ -174,15 +196,11 @@ function paintCar(car) {
   car.color = 'Red';
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use default arguments instead of short circuiting or conditionals
-Default arguments are often cleaner than short circuiting. Be aware that if you
-use them, your function will only provide default values for `undefined`
-arguments. Other "falsy" values such as `''`, `""`, `false`, `null`, `0`, and
-`NaN`, will not be replaced by a default value.
+### 使用默认变量替代短路运算或条件
 
-**Bad:**
+**不好的：**
 ```javascript
 function createMicrobrewery(name) {
   const breweryName = name || 'Hipster Brew Co.';
@@ -191,75 +209,81 @@ function createMicrobrewery(name) {
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
   // ...
 }
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+## **函数**
+
+### 函数参数 (两个以下最理想)
 
-## **Functions**
-### Function arguments (2 or fewer ideally)
 Limiting the amount of function parameters is incredibly important because it
 makes testing your function easier. Having more than three leads to a
 combinatorial explosion where you have to test tons of different cases with
 each separate argument.
 
-One or two arguments is the ideal case, and three should be avoided if possible.
-Anything more than that should be consolidated. Usually, if you have
+限制函数参数的个数是非常重要的， 因为这样将使你的函数容易进行测试。 一旦超过三个参数将会导致组
+合爆炸， 因为你不得不编写大量针对单个参数的测试用例。
+
+Zero arguments is the ideal case. One or two arguments is ok, and three should
+be avoided. Anything more than that should be consolidated. Usually, if you have
 more than two arguments then your function is trying to do too much. In cases
 where it's not, most of the time a higher-level object will suffice as an
 argument.
 
-Since JavaScript allows you to make objects on the fly, without a lot of class
+没有参数是最理想的， 一个或者两个参数也是可以的， 三个参数应该避免， 超过三个应该被重构。 通常，
+如果你有一个超过两个函数的参数， 那就意味着你的函数尝试做太多的事情。 如果不是， 多数情况下一个
+更高级对象可能会满足需求。
+
+Since JavaScript allows us to make objects on the fly, without a lot of class
 boilerplate, you can use an object if you are finding yourself needing a
 lot of arguments.
 
-To make it obvious what properties the function expects, you can use the ES2015/ES6
-destructuring syntax. This has a few advantages:
-
-1. When someone looks at the function signature, it's immediately clear what
-properties are being used.
-2. Destructuring also clones the specified primitive values of the argument
-object passed into the function. This can help prevent side effects. Note:
-objects and arrays that are destructured from the argument object are NOT
-cloned.
-3. Linters can warn you about unused properties, which would be impossible
-without destructuring.
+由于 JavaScript 允许我们不定义类型/模板就可以创建对象， 当你发现你自己需要大量的参数时， 你
+可以使用一个对象。
 
-**Bad:**
+**不好的：**
 ```javascript
 function createMenu(title, body, buttonText, cancellable) {
   // ...
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
-function createMenu({ title, body, buttonText, cancellable }) {
-  // ...
-}
-
-createMenu({
+const menuConfig = {
   title: 'Foo',
   body: 'Bar',
   buttonText: 'Baz',
   cancellable: true
-});
+};
+
+function createMenu(config) {
+  // ...
+}
+
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
 
+### 函数应当只做一件事情
 
-### Functions should do one thing
 This is by far the most important rule in software engineering. When functions
 do more than one thing, they are harder to compose, test, and reason about.
 When you can isolate a function to just one action, they can be refactored
 easily and your code will read much cleaner. If you take nothing else away from
 this guide other than this, you'll be ahead of many developers.
 
-**Bad:**
+这是软件工程中最重要的一条规则， 当函数需要做更多的事情时， 他们将会更难进行编写、 测试和推理。
+当你能将一个函数隔离到只有一个动作， 他们将能够被容易的进行重构并且你的代码将会更容易阅读。 如
+果你严格遵守本指南中的这一条， 你将会领先于许多开发者。
+
+**不好的：**
 ```javascript
 function emailClients(clients) {
   clients.forEach((client) => {
@@ -271,7 +295,7 @@ function emailClients(clients) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function emailClients(clients) {
   clients
@@ -284,11 +308,11 @@ function isClientActive(client) {
   return clientRecord.isActive();
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Function names should say what they do
+### 函数名称应该说明它要做什么
 
-**Bad:**
+**不好的：**
 ```javascript
 function addToDate(date, month) {
   // ...
@@ -296,11 +320,11 @@ function addToDate(date, month) {
 
 const date = new Date();
 
-// It's hard to to tell from the function name what is added
+// 很难从函数名看出加了什么
 addToDate(date, 1);
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function addMonthToDate(month, date) {
   // ...
@@ -309,14 +333,17 @@ function addMonthToDate(month, date) {
 const date = new Date();
 addMonthToDate(1, date);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+### 函数应该只有一个抽象级别
 
-### Functions should only be one level of abstraction
 When you have more than one level of abstraction your function is usually
 doing too much. Splitting up functions leads to reusability and easier
 testing.
 
-**Bad:**
+当在你的函数中有多于一个抽象级别时， 你的函数通常做了太多事情。 拆分函数将会提升重用性和测试性。
+
+**不好的：**
 ```javascript
 function parseBetterJSAlternative(code) {
   const REGEXES = [
@@ -342,7 +369,7 @@ function parseBetterJSAlternative(code) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function tokenize(code) {
   const REGEXES = [
@@ -377,31 +404,47 @@ function parseBetterJSAlternative(code) {
   });
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
+### 移除冗余代码
 
-### Remove duplicate code
 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
 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:**
+让这个抽象正确是关键的， 这是为什么要你遵循 *Classes* 那一章的 SOLID 的原因。 不好的抽象比冗
+余代码更差， 所以要谨慎行事。 既然已经这么说了， 如果你能够做出一个好的抽象， 才去做。 不要重复
+你自己， 否则你会发现当你要修改一个东西时时刻需要修改多个地方。
+
+**不好的：**
 ```javascript
 function showDeveloperList(developers) {
   developers.forEach((developer) => {
@@ -434,9 +477,9 @@ function showManagerList(managers) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
-function showEmployeeList(employees) {
+function showList(employees) {
   employees.forEach((employee) => {
     const expectedSalary = employee.calculateExpectedSalary();
     const experience = employee.getExperience();
@@ -457,11 +500,11 @@ function showEmployeeList(employees) {
   });
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Set default objects with Object.assign
+### 使用 Object.assign 设置默认对象
 
-**Bad:**
+**不好的：**
 ```javascript
 const menuConfig = {
   title: null,
@@ -480,7 +523,7 @@ function createMenu(config) {
 createMenu(menuConfig);
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const menuConfig = {
   title: 'Order',
@@ -503,13 +546,18 @@ function createMenu(config) {
 
 createMenu(menuConfig);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
+
 
+### 不要使用标记位做为函数参数
+Flags tell your user that this function does more than one thing. Functions
+should do one thing. Split out your functions if they are following different
+code paths based on a boolean.
 
-### Don't use flags as function parameters
-Flags tell your user that this function does more than one thing. Functions should do one thing. Split out your functions if they are following different code paths based on a boolean.
+标记位是告诉你的用户这个函数做了不只一件事情。 函数应该只做一件事情。 如果你的函数因为一个布尔值
+出现不同的代码路径， 请拆分它们。
 
-**Bad:**
+**不好的：**
 ```javascript
 function createFile(name, temp) {
   if (temp) {
@@ -520,7 +568,7 @@ function createFile(name, temp) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function createFile(name) {
   fs.create(name);
@@ -530,28 +578,41 @@ function createTempFile(name) {
   createFile(`./temp/${name}`);
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid Side Effects (part 1)
+### 避免副作用
 A function produces a side effect if it does anything other than take a value in
 and return another value or values. A side effect could be writing to a file,
 modifying some global variable, or accidentally wiring all your money to a
 stranger.
 
+如果一个函数做了除接受一个值然后返回一个值或多个值之外的任何事情， 它将会产生副作用， 它可能是
+写入一个文件， 修改一个全局变量， 或者意外的把你所有的钱连接到一个陌生人那里。
+
 Now, you do need to have side effects in a program on occasion. Like the previous
 example, you might need to write to a file. What you want to do is to
 centralize where you are doing this. Don't have several functions and classes
 that write to a particular file. Have one service that does it. One and only one.
 
+现在在你的程序中确实偶尔需要副作用， 就像上面的代码， 你也许需要写入到一个文件， 你需要做的是集
+中化你要做的事情， 不要让多个函数或者类写入一个特定的文件， 用一个服务来实现它， 一个并且只有一
+个。
+
 The main point is to avoid common pitfalls like sharing state between objects
 without any structure, using mutable data types that can be written to by anything,
 and not centralizing where your side effects occur. If you can do this, you will
 be happier than the vast majority of other programmers.
 
-**Bad:**
+重点是避免这些常见的易犯的错误， 比如在对象之间共享状态而不使用任何结构， 使用任何地方都可以写入
+的可变的数据类型， 没有集中化导致副作用。 如果你能做到这些， 那么你将会比其它的码农大军更加幸福。
+
+**不好的：**
 ```javascript
 // Global variable referenced by following function.
-// If we had another function that used this name, now it'd be an array and it could break it.
+// 全局变量被下面的函数引用
+// If we had another function that used this name, now it'd be an array and it
+// could break it.
+// 如果我们有另一个函数使用这个 name ， 现在它应该是一个数组， 这可能会出现错误。
 let name = 'Ryan McDermott';
 
 function splitIntoFirstAndLastName() {
@@ -563,7 +624,7 @@ splitIntoFirstAndLastName();
 console.log(name); // ['Ryan', 'McDermott'];
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function splitIntoFirstAndLastName(name) {
   return name.split(' ');
@@ -575,58 +636,9 @@ const newName = splitIntoFirstAndLastName(name);
 console.log(name); // 'Ryan McDermott';
 console.log(newName); // ['Ryan', 'McDermott'];
 ```
-**[⬆ back to top](#table-of-contents)**
-
-### Avoid Side Effects (part 2)
-In JavaScript, primitives are passed by value and objects/arrays are passed by
-reference. In the case of objects and arrays, if your function makes a change
-in a shopping cart array, for example, by adding an item to purchase,
-then any other function that uses that `cart` array will be affected by this
-addition. That may be great, however it can be bad too. Let's imagine a bad
-situation:
-
-The user clicks the "Purchase", button which calls a `purchase` function that
-spawns a network request and sends the `cart` array to the server. Because
-of a bad network connection, the `purchase` function has to keep retrying the
-request. Now, what if in the meantime the user accidentally clicks "Add to Cart"
-button on an item they don't actually want before the network request begins?
-If that happens and the network request begins, then that purchase function
-will send the accidentally added item because it has a reference to a shopping
-cart array that the `addItemToCart` function modified by adding an unwanted
-item.
-
-A great solution would be for the `addItemToCart` to always clone the `cart`,
-edit it, and return the clone. This ensures that no other functions that are
-holding onto a reference of the shopping cart will be affected by any changes.
-
-Two caveats to mention to this approach:
-  1. There might be cases where you actually want to modify the input object,
-but when you adopt this programming practice you will find that those case
-are pretty rare. Most things can be refactored to have no side effects!
-
-  2. Cloning big objects can be very expensive in terms of performance. Luckily,
-this isn't a big issue in practice because there are
-[great libraries](https://facebook.github.io/immutable-js/) that allow
-this kind of programming approach to be fast and not as memory intensive as
-it would be for you to manually clone objects and arrays.
-
-**Bad:**
-```javascript
-const addItemToCart = (cart, item) => {
-  cart.push({ item, date: Date.now() });
-};
-```
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-**Good:**
-```javascript
-const addItemToCart = (cart, item) => {
-  return [...cart, { item, date : Date.now() }];
-};
-```
-
-**[⬆ back to top](#table-of-contents)**
-
-### Don't write to global functions
+### 不要写入全局函数
 Polluting globals is a bad practice in JavaScript because you could clash with another
 library and the user of your API would be none-the-wiser until they get an
 exception in production. Let's think about an example: what if you wanted to
@@ -637,7 +649,14 @@ to do the same thing. What if that other library was just using `diff` to find
 the difference between the first and last elements of an array? This is why it
 would be much better to just use ES2015/ES6 classes and simply extend the `Array` global.
 
-**Bad:**
+污染全局在 JavaScript 中是一个不好的做法， 因为你可能会和另外一个类库冲突， 你的 API 的用户
+可能不够聪明， 直到他们得到在生产环境得到一个异常。 让我们来考虑这样一个例子： 假设你要扩展
+JavaScript 的 原生 `Array` ， 添加一个可以显示两个数组的不同之处的 `diff` 方法， 你可以在
+`Array.prototype` 中写一个新的方法， 但是它可能会和尝试做相同事情的其它类库发生冲突。 如果有
+另外一个类库仅仅使用 `diff` 方法来查找数组的第一个元素和最后一个元素之间的不同之处呢？ 这就是
+为什么使用 ES2015/ES6 的类是一个更好的做法的原因， 只要简单的扩展全局的 `Array` 即可。
+
+**不好的：**
 ```javascript
 Array.prototype.diff = function diff(comparisonArray) {
   const hash = new Set(comparisonArray);
@@ -645,7 +664,7 @@ Array.prototype.diff = function diff(comparisonArray) {
 };
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class SuperArray extends Array {
   diff(comparisonArray) {
@@ -654,14 +673,17 @@ class SuperArray extends Array {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Favor functional programming over imperative programming
+### 函数式编程优于指令式编程
 JavaScript isn't a functional language in the way that Haskell is, but it has
 a functional flavor to it. Functional languages are cleaner and easier to test.
 Favor this style of programming when you can.
 
-**Bad:**
+JavaScript 不是 Haskell 那种方式的函数式语言， 但是它有它的函数式风格。 函数式语言更加简洁
+并且更容易进行测试， 当你可以使用函数式编程风格时请尽情使用。
+
+**不好的：**
 ```javascript
 const programmerOutput = [
   {
@@ -686,7 +708,7 @@ for (let i = 0; i < programmerOutput.length; i++) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const programmerOutput = [
   {
@@ -704,24 +726,22 @@ const programmerOutput = [
   }
 ];
 
-const INITIAL_VALUE = 0;
-
 const totalOutput = programmerOutput
   .map((programmer) => programmer.linesOfCode)
-  .reduce((acc, linesOfCode) => acc + linesOfCode, INITIAL_VALUE);
+  .reduce((acc, linesOfCode) => acc + linesOfCode, 0);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Encapsulate conditionals
+### 封装条件语句
 
-**Bad:**
+**不好的：**
 ```javascript
 if (fsm.state === 'fetching' && isEmpty(listNode)) {
   // ...
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function shouldShowSpinner(fsm, listNode) {
   return fsm.state === 'fetching' && isEmpty(listNode);
@@ -731,11 +751,11 @@ if (shouldShowSpinner(fsmInstance, listNodeInstance)) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid negative conditionals
+### 避免负面条件
 
-**Bad:**
+**不好的：**
 ```javascript
 function isDOMNodeNotPresent(node) {
   // ...
@@ -746,7 +766,7 @@ if (!isDOMNodeNotPresent(node)) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function isDOMNodePresent(node) {
   // ...
@@ -756,9 +776,9 @@ if (isDOMNodePresent(node)) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid conditionals
+### 避免条件
 This seems like an impossible task. Upon first hearing this, most people say,
 "how am I supposed to do anything without an `if` statement?" The answer is that
 you can use polymorphism to achieve the same task in many cases. The second
@@ -768,7 +788,13 @@ one thing. When you have classes and functions that have `if` statements, you
 are telling your user that your function does more than one thing. Remember,
 just do one thing.
 
-**Bad:**
+这看起来似乎是一个不可能的任务。 第一次听到这个时， 多数人会说： “没有 `if` 语句还能期望我干
+啥呢”， 答案是多数情况下你可以使用多态来完成同样的任务。 第二个问题通常是 “好了， 那么做很棒，
+但是我为什么想要那样做呢”， 答案是我们学到的上一条代码整洁之道的理念： 一个函数应当只做一件事情。
+当你有使用 `if` 语句的类/函数是， 你在告诉你的用户你的函数做了不止一件事情。 记住： 只做一件
+事情。
+
+**不好的：**
 ```javascript
 class Airplane {
   // ...
@@ -785,7 +811,7 @@ class Airplane {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class Airplane {
   // ...
@@ -812,34 +838,37 @@ class Cessna extends Airplane {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid type-checking (part 1)
+### 避免类型检查 (part 1)
 JavaScript is untyped, which means your functions can take any type of argument.
 Sometimes you are bitten by this freedom and it becomes tempting to do
 type-checking in your functions. There are many ways to avoid having to do this.
 The first thing to consider is consistent APIs.
 
-**Bad:**
+JavaScript 是无类型的， 这意味着你的函数能接受任何类型的参数。 但是有时又会被这种自由咬伤，
+于是又尝试在你的函数中做类型检查。 有很多种方式来避免这个， 第一个要考虑的是一致的 API 。
+
+**不好的：**
 ```javascript
 function travelToTexas(vehicle) {
   if (vehicle instanceof Bicycle) {
-    vehicle.pedal(this.currentLocation, new Location('texas'));
+    vehicle.peddle(this.currentLocation, new Location('texas'));
   } else if (vehicle instanceof Car) {
     vehicle.drive(this.currentLocation, new Location('texas'));
   }
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function travelToTexas(vehicle) {
   vehicle.move(this.currentLocation, new Location('texas'));
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid type-checking (part 2)
+### 避免类型检查 (part 2)
 If you are working with basic primitive values like strings, integers, and arrays,
 and you can't use polymorphism but you still feel the need to type-check,
 you should consider using TypeScript. It is an excellent alternative to normal
@@ -850,7 +879,13 @@ doesn't make up for the lost readability. Keep your JavaScript clean, write
 good tests, and have good code reviews. Otherwise, do all of that but with
 TypeScript (which, like I said, is a great alternative!).
 
-**Bad:**
+如果你使用原始的字符串、 整数和数组， 并且你不能使用多态， 但是你依然感觉到有类型检查的需要，
+你应该考虑使用 TypeScript 。 它是一个常规 JavaScript 的优秀的替代品， 因为它在标准的 JavaScript
+语法之上为你提供静态类型。 对常规 JavaScript 做人工类型检查的问题是需要大量的冗词来仿造类型安
+全而不缺失可读性。 保持你的 JavaScript 简洁， 编写良好的测试， 并有良好的代码审阅， 否则使用
+TypeScript （就像我说的， 它是一个伟大的替代品）来完成这些。
+
+**不好的：**
 ```javascript
 function combine(val1, val2) {
   if (typeof val1 === 'number' && typeof val2 === 'number' ||
@@ -862,45 +897,54 @@ function combine(val1, val2) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function combine(val1, val2) {
   return val1 + val2;
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't over-optimize
+### 不要过度优化
 Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
 times, if you are optimizing then you are just wasting your time. [There are good
 resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)
 for seeing where optimization is lacking. Target those in the meantime, until
 they are fixed if they can be.
 
-**Bad:**
+现代化浏览器运行时在幕后做大量的优化， 在大多数的时间， 做优化就是在浪费你的时间。 [这些是好的
+资源](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)， 用来
+查看那些地方需要优化。 为这些而优化， 直到他们被修正。
+
+**不好的：**
 ```javascript
 
 // On old browsers, each iteration with uncached `list.length` would be costly
 // because of `list.length` recomputation. In modern browsers, this is optimized.
+// 在旧的浏览器上， 每次循环 `list.length` 都没有被缓存， 会导致不必要的开销， 因为要重新计
+// 算 `list.length` 。 在现代化浏览器上， 这个已经被优化了。
 for (let i = 0, len = list.length; i < len; i++) {
   // ...
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 for (let i = 0; i < list.length; i++) {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Remove dead code
+### 移除僵尸代码
 Dead code is just as bad as duplicate code. There's no reason to keep it in
 your codebase. If it's not being called, get rid of it! It will still be safe
 in your version history if you still need it.
 
-**Bad:**
+僵死代码和冗余代码同样糟糕。 没有理由在代码库中保存它。 如果它不会被调用， 就删掉它。 当你需要
+它时， 它依然保存在版本历史记录中。
+
+**不好的：**
 ```javascript
 function oldRequestModule(url) {
   // ...
@@ -915,7 +959,7 @@ inventoryTracker('apples', req, 'www.inventory-awesome.io');
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function newRequestModule(url) {
   // ...
@@ -924,72 +968,89 @@ function newRequestModule(url) {
 const req = newRequestModule;
 inventoryTracker('apples', req, 'www.inventory-awesome.io');
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Objects and Data Structures**
-### Use getters and setters
-Using getters and setters to access data on objects could be better than simply
+## **对象和数据结构**
+### 使用 getters 和 setters
+JavaScript doesn't have interfaces or types so it is very hard to enforce this
+pattern, because we don't have keywords like `public` and `private`. As it is,
+using getters and setters to access data on objects is far better than simply
 looking for a property on an object. "Why?" you might ask. Well, here's an
 unorganized list of reasons why:
 
+JavaScript 没有接口或类型， 所以坚持这个模式是非常困难的， 因为我们没有 `public` 和 `private`
+关键字。 正因为如此， 使用 getters 和 setters 来访问对象上的数据比简单的在一个对象上查找属性
+要好得多。 “为什么？” 你可能会问， 好吧， 原因请看下面的列表：
+
 * When you want to do more beyond getting an object property, you don't have
 to look up and change every accessor in your codebase.
 * Makes adding validation simple when doing a `set`.
 * Encapsulates the internal representation.
 * Easy to add logging and error handling when getting and setting.
+* Inheriting this class, you can override default functionality.
 * You can lazy load your object's properties, let's say getting it from a
 server.
 
+* 当你想在获取一个对象属性的背后做更多的事情时， 你不需要在代码库中查找和修改每一处访问；
+* 使用 `set` 可以让添加验证变得容易；
+* 封装内部实现；
+* 使用 getting 和 setting 时， 容易添加日志和错误处理；
+* 继承这个类， 你可以重写默认功能；
+* 你可以延迟加载对象的属性， 比如说从服务器获取。
 
-**Bad:**
+**不好的：**
 ```javascript
-function makeBankAccount() {
-  // ...
-
-  return {
-    balance: 0,
-    // ...
-  };
+class BankAccount {
+  constructor() {
+    this.balance = 1000;
+  }
 }
 
-const account = makeBankAccount();
-account.balance = 100;
+const bankAccount = new BankAccount();
+
+// Buy shoes...
+bankAccount.balance -= 100;
 ```
 
-**Good:**
+**好的：**
 ```javascript
-function makeBankAccount() {
-  // this one is private
-  let balance = 0;
+class BankAccount {
+  constructor(balance = 1000) {
+    this._balance = balance;
+  }
 
-  // a "getter", made public via the returned object below
-  function getBalance() {
-    return balance;
+  // It doesn't have to be prefixed with `get` or `set` to be a getter/setter
+  set balance(amount) {
+    if (verifyIfAmountCanBeSetted(amount)) {
+      this._balance = amount;
+    }
   }
 
-  // a "setter", made public via the returned object below
-  function setBalance(amount) {
-    // ... validate before updating the balance
-    balance = amount;
+  get balance() {
+    return this._balance;
   }
 
-  return {
+  verifyIfAmountCanBeSetted(val) {
     // ...
-    getBalance,
-    setBalance,
-  };
+  }
 }
 
-const account = makeBankAccount();
-account.setBalance(100);
+const bankAccount = new BankAccount();
+
+// Buy shoes...
+bankAccount.balance -= shoesPrice;
+
+// Get balance
+let balance = bankAccount.balance;
+
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Make objects have private members
-This can be accomplished through closures (for ES5 and below).
+### 让对象拥有私有成员
+这个可以通过闭包来实现（针对 ES5 或更低）。
 
-**Bad:**
+**不好的：**
 ```javascript
 
 const Employee = function(name) {
@@ -1006,32 +1067,34 @@ delete employee.name;
 console.log(`Employee name: ${employee.getName()}`); // Employee name: undefined
 ```
 
-**Good:**
+**好的：**
 ```javascript
-function makeEmployee(name) {
-  return {
-    getName() {
-      return name;
-    },
+const Employee = function (name) {
+  this.getName = function getName() {
+    return name;
   };
-}
+};
 
-const employee = makeEmployee('John Doe');
+const employee = new Employee('John Doe');
 console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 delete employee.name;
 console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Classes**
-### Prefer ES2015/ES6 classes over ES5 plain functions
+## **类**
+### ES2015/ES6 类优先与 ES5 纯函数
 It's very difficult to get readable class inheritance, construction, and method
 definitions for classical ES5 classes. If you need inheritance (and be aware
-that you might not), then prefer ES2015/ES6 classes. However, prefer small functions over
+that you might not), then prefer classes. However, prefer small functions over
 classes until you find yourself needing larger and more complex objects.
 
-**Bad:**
+很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
+要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
+对象。
+
+**不好的：**
 ```javascript
 const Animal = function(age) {
   if (!(this instanceof Animal)) {
@@ -1070,7 +1133,7 @@ Human.prototype.constructor = Human;
 Human.prototype.speak = function speak() {};
 ```
 
-**Good:**
+**好的**
 ```javascript
 class Animal {
   constructor(age) {
@@ -1098,17 +1161,21 @@ class Human extends Mammal {
   speak() { /* ... */ }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
-
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Use method chaining
+### 使用方法链
 This pattern is very useful in JavaScript and you see it in many libraries such
 as jQuery and Lodash. It allows your code to be expressive, and less verbose.
 For that reason, I say, use method chaining and take a look at how clean your code
 will be. In your class functions, simply return `this` at the end of every function,
 and you can chain further class methods onto it.
 
-**Bad:**
+这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
+它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
+会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
+其它方法链在一起。
+
+**不好的：**
 ```javascript
 class Car {
   constructor() {
@@ -1141,7 +1208,7 @@ car.setModel('F-150');
 car.save();
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class Car {
   constructor() {
@@ -1181,9 +1248,9 @@ const car = new Car()
   .setModel('F-150')
   .save();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Prefer composition over inheritance
+### 组合优先于继承
 As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
 you should prefer composition over inheritance where you can. There are lots of
 good reasons to use inheritance and lots of good reasons to use composition.
@@ -1191,17 +1258,30 @@ The main point for this maxim is that if your mind instinctively goes for
 inheritance, try to think if composition could model your problem better. In some
 cases it can.
 
+正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
+你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
+的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
+可以。
+
 You might be wondering then, "when should I use inheritance?" It
 depends on your problem at hand, but this is a decent list of when inheritance
 makes more sense than composition:
 
+那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
+明什么时候继承比组合更好用：
+
 1. Your inheritance represents an "is-a" relationship and not a "has-a"
 relationship (Human->Animal vs. User->UserDetails).
 2. You can reuse code from the base classes (Humans can move like all animals).
 3. You want to make global changes to derived classes by changing a base class.
 (Change the caloric expenditure of all animals when they move).
 
-**Bad:**
+
+1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
+2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
+3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
+
+**不好的：**
 ```javascript
 class Employee {
   constructor(name, email) {
@@ -1213,6 +1293,7 @@ class Employee {
 }
 
 // Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
+// 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
 class EmployeeTaxData extends Employee {
   constructor(ssn, salary) {
     super();
@@ -1224,7 +1305,7 @@ class EmployeeTaxData extends Employee {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class EmployeeTaxData {
   constructor(ssn, salary) {
@@ -1247,20 +1328,25 @@ class Employee {
   // ...
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **SOLID**
-### Single Responsibility Principle (SRP)
+### 单一职责原则 (SRP)
 As stated in Clean Code, "There should never be more than one reason for a class
 to change". It's tempting to jam-pack a class with a lot of functionality, like
 when you can only take one suitcase on your flight. The issue with this is
 that your class won't be conceptually cohesive and it will give it many reasons
 to change. Minimizing the amount of times you need to change a class is important.
-It's important because if too much functionality is in one class and you modify
-a piece of it, it can be difficult to understand how that will affect other
-dependent modules in your codebase.
+It's important because if too much functionality is in one class and you modify a piece of it,
+it can be difficult to understand how that will affect other dependent modules in
+your codebase.
 
-**Bad:**
+正如代码整洁之道所述， “永远不要有超过一个理由来修改一个类”。 给一个类塞满许多功能， 就像你在航
+班上只能带一个行李箱一样， 这样做的问题你的类不会有理想的内聚性， 将会有太多的理由来对它进行修改。
+最小化需要修改一个类的次数时很重要的， 因为如果一个类拥有太多的功能， 一旦你修改它的一小部分，
+将会很难弄清楚会对代码库中的其它模块造成什么影响。
+
+**好的：**
 ```javascript
 class UserSettings {
   constructor(user) {
@@ -1279,7 +1365,7 @@ class UserSettings {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class UserAuth {
   constructor(user) {
@@ -1305,15 +1391,18 @@ class UserSettings {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Open/Closed Principle (OCP)
+### 开闭原则 (OCP)
 As stated by Bertrand Meyer, "software entities (classes, modules, functions,
 etc.) should be open for extension, but closed for modification." What does that
 mean though? This principle basically states that you should allow users to
 add new functionalities without changing existing code.
 
-**Bad:**
+Bertrand Meyer 说过， “软件实体 (类， 模块， 函数等) 应该为扩展开放， 但是为修改关闭。” 这
+是什么意思呢？ 这个原则基本上说明了你应该允许用户添加功能而不必修改现有的代码。
+
+**不好的：**
 ```javascript
 class AjaxAdapter extends Adapter {
   constructor() {
@@ -1356,7 +1445,7 @@ function makeHttpCall(url) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class AjaxAdapter extends Adapter {
   constructor() {
@@ -1392,15 +1481,19 @@ class HttpRequester {
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Liskov Substitution Principle (LSP)
+### 里氏代换原则 (LSP)
 This is a scary term for a very simple concept. It's formally defined as "If S
 is a subtype of T, then objects of type T may be replaced with objects of type S
 (i.e., objects of type S may substitute objects of type T) without altering any
 of the desirable properties of that program (correctness, task performed,
 etc.)." That's an even scarier definition.
 
+这是针对一个非常简单的里面的一个恐怖意图， 它的正式定义是： “如果 S 是 T 的一个子类型， 那么类
+型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）儿不需
+要修改目标程序的期望性质 （正确性、 任务执行性等）。” 这甚至是个恐怖的定义。
+
 The best explanation for this is if you have a parent class and a child class,
 then the base class and child class can be used interchangeably without getting
 incorrect results. This might still be confusing, so let's take a look at the
@@ -1408,7 +1501,11 @@ classic Square-Rectangle example. Mathematically, a square is a rectangle, but
 if you model it using the "is-a" relationship via inheritance, you quickly
 get into trouble.
 
-**Bad:**
+最好的解释是， 如果你又一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
+能还有有些疑惑， 让我们来看一下这个经典的正方形与矩形的例子。 从数学上说， 一个正方形是一个矩形，
+但是你用 "is-a" 的关系用继承来实现， 你将很快遇到麻烦。
+
+**不好的：**
 ```javascript
 class Rectangle {
   constructor() {
@@ -1453,7 +1550,7 @@ function renderLargeRectangles(rectangles) {
   rectangles.forEach((rectangle) => {
     rectangle.setWidth(4);
     rectangle.setHeight(5);
-    const area = rectangle.getArea(); // BAD: Returns 25 for Square. Should be 20.
+    const area = rectangle.getArea(); // BAD: Will return 25 for Square. Should be 20.
     rectangle.render(area);
   });
 }
@@ -1462,7 +1559,7 @@ const rectangles = [new Rectangle(), new Rectangle(), new Square()];
 renderLargeRectangles(rectangles);
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class Shape {
   setColor(color) {
@@ -1507,24 +1604,33 @@ function renderLargeShapes(shapes) {
 const shapes = [new Rectangle(4, 5), new Rectangle(4, 5), new Square(5)];
 renderLargeShapes(shapes);
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Interface Segregation Principle (ISP)
+### 接口隔离原则 (ISP)
 JavaScript doesn't have interfaces so this principle doesn't apply as strictly
 as others. However, it's important and relevant even with JavaScript's lack of
 type system.
 
+JavaScript 没有接口， 所以这个原则不想其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
+型的语言来说， 它依然是重要并且有意义的。
+
 ISP states that "Clients should not be forced to depend upon interfaces that
 they do not use." Interfaces are implicit contracts in JavaScript because of
 duck typing.
 
+接口隔离原则说的是 “客户端不应该强制依赖他们不需要的接口。” 在 JavaScript 这种弱类型语言中，
+接口是隐式的契约。
+
 A good example to look at that demonstrates this principle in JavaScript is for
 classes that require large settings objects. Not requiring clients to setup
 huge amounts of options is beneficial, because most of the time they won't need
-all of the settings. Making them optional helps prevent having a
-"fat interface".
+all of the settings. Making them optional helps prevent having a "fat interface".
 
-**Bad:**
+在 JavaScript 中能比较好的说明这个原则的是一个类需要一个巨大的配置对象。 不需要客户端去设置大
+量的选项是有益的， 因为多数情况下他们不需要全部的设置。 让它们变成可选的有助于防止出现一个“胖接
+口”。
+
+**不好的：**
 ```javascript
 class DOMTraverser {
   constructor(settings) {
@@ -1550,7 +1656,7 @@ const $ = new DOMTraverser({
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class DOMTraverser {
   constructor(settings) {
@@ -1582,15 +1688,19 @@ const $ = new DOMTraverser({
   }
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Dependency Inversion Principle (DIP)
+### 依赖反转原则 (DIP)
 This principle states two essential things:
 1. High-level modules should not depend on low-level modules. Both should
 depend on abstractions.
 2. Abstractions should not depend upon details. Details should depend on
 abstractions.
 
+这个原则阐述了两个重要的事情：
+1. 高级模块不应该依赖于低级模块， 两者都应该依赖与抽象；
+2. 抽象不应当依赖于具体实现， 具体实现应当依赖于抽象。
+
 This can be hard to understand at first, but if you've worked with Angular.js,
 you've seen an implementation of this principle in the form of Dependency
 Injection (DI). While they are not identical concepts, DIP keeps high-level
@@ -1599,13 +1709,22 @@ It can accomplish this through DI. A huge benefit of this is that it reduces
 the coupling between modules. Coupling is a very bad development pattern because
 it makes your code hard to refactor.
 
+这个一开始会很难理解， 但是如果你使用过 Angular.js ， 你应该已经看到过通过依赖注入来实现的这
+个原则， 虽然他们不是相同的概念， 依赖反转原则让高级模块远离低级模块的细节和创建， 可以通过 DI
+来实现。 这样做的巨大益处是降低模块间的耦合。 耦合是一个非常糟糕的开发模式， 因为会导致代码难于
+重构。
+
 As stated previously, JavaScript doesn't have interfaces so the abstractions
 that are depended upon are implicit contracts. That is to say, the methods
 and properties that an object/class exposes to another object/class. In the
 example below, the implicit contract is that any Request module for an
 `InventoryTracker` will have a `requestItems` method.
 
-**Bad:**
+如上所述， JavaScript 没有接口， 所以被依赖的抽象是隐式契约。 也就是说， 一个对象/类的方法和
+属性直接暴露给另外一个对象/类。 在下面的例子中， 任何一个 Request 模块的隐式契约 `InventoryTracker`
+将有一个 `requestItems` 方法。
+
+**不好的：**
 ```javascript
 class InventoryRequester {
   constructor() {
@@ -1623,6 +1742,8 @@ class InventoryTracker {
 
     // BAD: We have created a dependency on a specific request implementation.
     // We should just have requestItems depend on a request method: `request`
+    // 不好的： 我们已经创建了一个对请求的具体实现的依赖， 我们只有一个 requestItems 方法依
+    // 赖一个请求方法 'request'
     this.requester = new InventoryRequester();
   }
 
@@ -1637,7 +1758,7 @@ const inventoryTracker = new InventoryTracker(['apples', 'bananas']);
 inventoryTracker.requestItems();
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class InventoryTracker {
   constructor(items, requester) {
@@ -1674,12 +1795,14 @@ class InventoryRequesterV2 {
 
 // By constructing our dependencies externally and injecting them, we can easily
 // substitute our request module for a fancy new one that uses WebSockets.
+// 通过外部创建依赖项并将它们注入， 我们可以轻松的用一个崭新的使用 WebSockets 的请求模块进行
+// 替换。
 const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
 inventoryTracker.requestItems();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Testing**
+## **测试**
 Testing is more important than shipping. If you have no tests or an
 inadequate amount, then every time you ship code you won't be sure that you
 didn't break anything. Deciding on what constitutes an adequate amount is up
@@ -1688,6 +1811,10 @@ you achieve very high confidence and developer peace of mind. This means that
 in addition to having a great testing framework, you also need to use a
 [good coverage tool](http://gotwarlost.github.io/istanbul/).
 
+测试比发布更加重要。 如果你没有测试或者测试不够充分， 每次发布时你就不能确认没有破坏任何事情。
+测试的量由你的团队决定， 但是拥有 100% 的覆盖率(包括所有的语句和分支)是你为什么能达到高度自信
+和内心的平静。 这意味着需要一个额外的伟大的测试框架， 也需要一个好的[覆盖率工具](http://gotwarlost.github.io/istanbul/)。
+
 There's no excuse to not write tests. There's [plenty of good JS test frameworks]
 (http://jstherightway.org/#testing-tools), so find one that your team prefers.
 When you find one that works for your team, then aim to always write tests
@@ -1696,11 +1823,16 @@ Test Driven Development (TDD), that is great, but the main point is to just
 make sure you are reaching your coverage goals before launching any feature,
 or refactoring an existing one.
 
-### Single concept per test
+没有理由不写测试。 这里有[大量的优秀的 JS 测试框架](http://jstherightway.org/#testing-tools)，
+选一个适合你的团队的即可。 当为团队选择了测试框架之后， 接下来的目标是为生产的每一个新的功能／模
+块编写测试。 如果你倾向于测试驱动开发(TDD)， 那就太棒了， 但是要点是确认你在上线任何功能或者重
+构一个现有功能之前， 达到了需要的目标覆盖率。
+
+### 一个测试一个概念
 
-**Bad:**
+**不好的：**
 ```javascript
-import assert from 'assert';
+const assert = require('assert');
 
 describe('MakeMomentJSGreatAgain', () => {
   it('handles date boundaries', () => {
@@ -1708,7 +1840,7 @@ describe('MakeMomentJSGreatAgain', () => {
 
     date = new MakeMomentJSGreatAgain('1/1/2015');
     date.addDays(30);
-    assert.equal('1/31/2015', date);
+    date.shouldEqual('1/31/2015');
 
     date = new MakeMomentJSGreatAgain('2/1/2016');
     date.addDays(28);
@@ -1721,15 +1853,15 @@ describe('MakeMomentJSGreatAgain', () => {
 });
 ```
 
-**Good:**
+**好的：**
 ```javascript
-import assert from 'assert';
+const assert = require('assert');
 
 describe('MakeMomentJSGreatAgain', () => {
   it('handles 30-day months', () => {
     const date = new MakeMomentJSGreatAgain('1/1/2015');
     date.addDays(30);
-    assert.equal('1/31/2015', date);
+    date.shouldEqual('1/31/2015');
   });
 
   it('handles leap year', () => {
@@ -1745,23 +1877,23 @@ describe('MakeMomentJSGreatAgain', () => {
   });
 });
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Concurrency**
-### Use Promises, not callbacks
+## **并发**
+### 使用 Promises, 不要使用回调
 Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
 Promises are a built-in global type. Use them!
 
-**Bad:**
-```javascript
-import { get } from 'request';
-import { writeFile } from 'fs';
+回调不够简洁， 因为他们会产生过多的嵌套。 在 ES2015/ES6 中， Promises 已经是内置的全局类型
+了，使用它们吧！
 
-get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response) => {
+**不好的：**
+```javascript
+require('request').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response) => {
   if (requestErr) {
     console.error(requestErr);
   } else {
-    writeFile('article.html', response.body, (writeErr) => {
+    require('fs').writeFile('article.html', response.body, (writeErr) => {
       if (writeErr) {
         console.error(writeErr);
       } else {
@@ -1773,14 +1905,11 @@ get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin', (requestErr, response)
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
-import { get } from 'request';
-import { writeFile } from 'fs';
-
-get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
+require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
   .then((response) => {
-    return writeFile('article.html', response);
+    return require('fs-promise').writeFile('article.html', response);
   })
   .then(() => {
     console.log('File written');
@@ -1790,23 +1919,24 @@ get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
   });
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Async/Await are even cleaner than Promises
+### Async/Await 比 Promises 更加简洁
 Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
 which offer an even cleaner solution. All you need is a function that is prefixed
 in an `async` keyword, and then you can write your logic imperatively without
 a `then` chain of functions. Use this if you can take advantage of ES2017/ES8 features
 today!
 
-**Bad:**
-```javascript
-import { get } from 'request-promise';
-import { writeFile } from 'fs-promise';
+Promises 是回调的一个非常简洁的替代品， 但是 ES2017/ES8 带来的 async 和 await 提供了一个
+更加简洁的解决方案。 你需要的只是一个前缀为 `async` 关键字的函数， 接下来就可以不需要 `then`
+函数链来编写逻辑了。 如果你能使用 ES2017/ES8 的高级功能的话， 今天就使用它吧！
 
-get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
+**不好的：**
+```javascript
+require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
   .then((response) => {
-    return writeFile('article.html', response);
+    return require('fs-promise').writeFile('article.html', response);
   })
   .then(() => {
     console.log('File written');
@@ -1817,31 +1947,31 @@ get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin')
 
 ```
 
-**Good:**
+**好的：**
 ```javascript
-import { get } from 'request-promise';
-import { writeFile } from 'fs-promise';
-
 async function getCleanCodeArticle() {
   try {
-    const response = await get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin');
-    await writeFile('article.html', response);
+    const response = await require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Martin');
+    await require('fs-promise').writeFile('article.html', response);
     console.log('File written');
   } catch(err) {
     console.error(err);
   }
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Error Handling**
+## **错误处理**
 Thrown errors are a good thing! They mean the runtime has successfully
 identified when something in your program has gone wrong and it's letting
 you know by stopping function execution on the current stack, killing the
 process (in Node), and notifying you in the console with a stack trace.
 
-### Don't ignore caught errors
+抛出错误是一件好事情！ 他们意味着当你的程序有错时运行时可以成功确认， 并且通过停止执行当前堆栈
+上的函数来让你知道， 结束当前进程（在 Node 中）， 在控制台中用一个堆栈跟踪提示你。
+
+### 不要忽略捕捉到的错误
 Doing nothing with a caught error doesn't give you the ability to ever fix
 or react to said error. Logging the error to the console (`console.log`)
 isn't much better as often times it can get lost in a sea of things printed
@@ -1849,7 +1979,11 @@ to the console. If you wrap any bit of code in a `try/catch` it means you
 think an error may occur there and therefore you should have a plan,
 or create a code path, for when it occurs.
 
-**Bad:**
+对捕捉到的错误不做任何处理不能给你修复错误或者响应错误的能力。 向控制台记录错误 (`console.log`)
+也不怎么好， 因为往往会丢失在海量的控制台输出中。 如果你把任意一段代码用 `try/catch` 包装那就
+意味着你想到这里可能会错， 因此你应该有个修复计划， 或者当错误发生时有一个代码路径。
+
+**不好的：**
 ```javascript
 try {
   functionThatMightThrow();
@@ -1858,7 +1992,7 @@ try {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 try {
   functionThatMightThrow();
@@ -1873,57 +2007,68 @@ try {
 }
 ```
 
-### Don't ignore rejected promises
+### 不要忽略被拒绝的 promise 
 For the same reason you shouldn't ignore caught errors
 from `try/catch`.
 
-**Bad:**
+与你不应忽略来自 `try/catch` 的错误的原因相同。
+
+**不好的：**
 ```javascript
 getdata()
-  .then((data) => {
-    functionThatMightThrow(data);
-  })
-  .catch((error) => {
-    console.log(error);
-  });
+.then((data) => {
+  functionThatMightThrow(data);
+})
+.catch((error) => {
+  console.log(error);
+});
 ```
 
-**Good:**
+**好的：**
 ```javascript
 getdata()
-  .then((data) => {
-    functionThatMightThrow(data);
-  })
-  .catch((error) => {
-    // One option (more noisy than console.log):
-    console.error(error);
-    // Another option:
-    notifyUserOfError(error);
-    // Another option:
-    reportErrorToService(error);
-    // OR do all three!
-  });
+.then((data) => {
+  functionThatMightThrow(data);
+})
+.catch((error) => {
+  // One option (more noisy than console.log):
+  console.error(error);
+  // Another option:
+  notifyUserOfError(error);
+  // Another option:
+  reportErrorToService(error);
+  // OR do all three!
+});
 ```
 
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-## **Formatting**
+## **格式化**
 Formatting is subjective. Like many rules herein, there is no hard and fast
 rule that you must follow. The main point is DO NOT ARGUE over formatting.
 There are [tons of tools](http://standardjs.com/rules.html) to automate this.
 Use one! It's a waste of time and money for engineers to argue over formatting.
 
+格式化是主观的。 就像其它规则一样， 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论， 这
+里有[大量的工具](http://standardjs.com/rules.html)来自动格式化， 使用其中的一个即可！ 因
+为做为工程师去争论格式化就是在浪费时间和金钱。
+
 For things that don't fall under the purview of automatic formatting
 (indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
 for some guidance.
 
-### Use consistent capitalization
+针对自动格式化工具不能涵盖的问题（缩进、 制表符还是空格、 双引号还是单引号等）， 这里有一些指南。
+
+### 使用一致的大小写
 JavaScript is untyped, so capitalization tells you a lot about your variables,
 functions, etc. These rules are subjective, so your team can choose whatever
 they want. The point is, no matter what you all choose, just be consistent.
 
-**Bad:**
+JavaScript 是无类型的， 所以大小写告诉你关于你的变量、 函数等的很多事情。 这些规则是主观的，
+所以你的团队可以选择他们想要的。 重点是， 不管你们选择了什么， 要保持一致。
+
+**不好的：**
 ```javascript
 const DAYS_IN_WEEK = 7;
 const daysInMonth = 30;
@@ -1938,7 +2083,7 @@ class animal {}
 class Alpaca {}
 ```
 
-**Good:**
+**好的：**
 ```javascript
 const DAYS_IN_WEEK = 7;
 const DAYS_IN_MONTH = 30;
@@ -1952,15 +2097,19 @@ function restoreDatabase() {}
 class Animal {}
 class Alpaca {}
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 
-### Function callers and callees should be close
+### 函数的调用方与被调用方应该靠近
 If a function calls another, keep those functions vertically close in the source
 file. Ideally, keep the caller right above the callee. We tend to read code from
 top-to-bottom, like a newspaper. Because of this, make your code read that way.
 
-**Bad:**
+如果一个函数调用另一个， 则在代码中这两个函数的竖直位置应该靠近。 理想情况下，保持被调用函数在被
+调用函数的正上方。 我们倾向于从上到下阅读代码， 就像读一章报纸。 由于这个原因， 保持你的代码可
+以按照这种方式阅读。
+
+**不好的：**
 ```javascript
 class PerformanceReview {
   constructor(employee) {
@@ -1999,7 +2148,7 @@ const review = new PerformanceReview(user);
 review.perfReview();
 ```
 
-**Good:**
+**好的：**
 ```javascript
 class PerformanceReview {
   constructor(employee) {
@@ -2038,13 +2187,15 @@ const review = new PerformanceReview(employee);
 review.perfReview();
 ```
 
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **Comments**
-### Only comment things that have business logic complexity.
+## **评论**
+### 仅仅对包含复杂业务逻辑的东西进行评论
 Comments are an apology, not a requirement. Good code *mostly* documents itself.
 
-**Bad:**
+评论是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
+
+**不好的：**
 ```javascript
 function hashIt(data) {
   // The hash
@@ -2065,7 +2216,7 @@ function hashIt(data) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 
 function hashIt(data) {
@@ -2082,12 +2233,14 @@ function hashIt(data) {
 }
 
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't leave commented out code in your codebase
+### 不要在代码库中保存注释掉的代码
 Version control exists for a reason. Leave old code in your history.
 
-**Bad:**
+因为有版本控制， 把旧的代码留在历史记录即可。
+
+**不好的：**
 ```javascript
 doStuff();
 // doOtherStuff();
@@ -2095,17 +2248,20 @@ doStuff();
 // doSoMuchStuff();
 ```
 
-**Good:**
+**好的：**
 ```javascript
 doStuff();
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Don't have journal comments
+### 不要有日志式的评论
 Remember, use version control! There's no need for dead code, commented code,
 and especially journal comments. Use `git log` to get history!
 
-**Bad:**
+记住， 使用版本控制！ 不需要僵尸代码， 注释调的代码， 尤其是日志式的评论。 使用 `git log` 来
+获取历史记录。
+
+**不好的：**
 ```javascript
 /**
  * 2016-12-20: Removed monads, didn't understand them (RM)
@@ -2118,19 +2274,21 @@ function combine(a, b) {
 }
 ```
 
-**Good:**
+**好的：**
 ```javascript
 function combine(a, b) {
   return a + b;
 }
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### Avoid positional markers
+### 避免占位符
 They usually just add noise. Let the functions and variable names along with the
 proper indentation and formatting give the visual structure to your code.
 
-**Bad:**
+它们仅仅添加了干扰。 让函数和变量名称与合适的缩进和格式化为你的代码提供视觉结构。
+
+**不好的：**
 ```javascript
 ////////////////////////////////////////////////////////////////////////////////
 // Scope Model Instantiation
@@ -2148,7 +2306,7 @@ const actions = function() {
 };
 ```
 
-**Good:**
+**好的：**
 ```javascript
 $scope.model = {
   menu: 'foo',
@@ -2159,7 +2317,7 @@ const actions = function() {
   // ...
 };
 ```
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## Translation
 
@@ -2176,4 +2334,4 @@ This is also available in other languages:
     - [maksugr/clean-code-javascript](https://github.com/maksugr/clean-code-javascript)
   - ![vi](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png) **Vietnamese**: [hienvd/clean-code-javascript/](https://github.com/hienvd/clean-code-javascript/)
 
-**[⬆ back to top](#table-of-contents)**
+**[⬆ 返回顶部](#代码整洁的-javascript)**

From 00176ef05d10911de7cf2d377a097c30baad414e Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Wed, 15 Feb 2017 14:10:20 +0800
Subject: [PATCH 49/54] review part 1

---
 README.md | 32 ++++++--------------------------
 1 file changed, 6 insertions(+), 26 deletions(-)

diff --git a/README.md b/README.md
index 17090f51..4b1c4e96 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,7 @@
 # 代码整洁的 JavaScript
 
 ## 目录
+
   1. [简介](#简介)
   2. [变量](#变量)
   3. [函数](#函数)
@@ -15,48 +16,27 @@
   12. [Translation](#translation)
 
 ## 简介
-![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](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.
+![一张用你阅读代码时吐槽的数量来评估软件质量的搞笑图片](http://www.osnews.com/images/comics/wtfm.jpg)
 
 将源自 Robert C. Martin 的 [*Clean Code*](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
-的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个用 JavaScript 来生产可
-读的， 可重用的， 以及可重构的软件的指南。
-
-Not every principle herein has to be strictly followed, and even fewer 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*.
+的软件工程原则适配到 JavaScript 。 这不是一个代码风格指南， 它是一个使用 JavaScript 来生产
+可读的， 可重用的， 以及可重构的软件的指南。
 
 这里的每一项原则都不是必须遵守的， 甚至只有更少的能够被广泛认可。 这些仅仅是指南而已， 但是却是
 *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.
-
 我们的软件工程行业只有短短的 50 年， 依然有很多要我们去学习。 当软件架构与建筑架构一样古老时，
 也许我们将会有硬性的规则去遵守。 而现在， 让这些指南做为你和你的团队生产的 JavaScript 代码的
 质量的标准。
 
-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!
-
 还有一件事： 知道这些指南并不能马上让你成为一个更加出色的软件开发者， 并且使用它们工作多年也并
-不意味着你不会犯错误。 每一段代码最开始都是草稿， 像湿粘土一样被打造成最终的形态。 最后当我们
+不意味着你不再会犯错误。 每一段代码最开始都是草稿， 像湿粘土一样被打造成最终的形态。 最后当我们
 和搭档们一起审查代码时清除那些不完善之处。 不要因为最初需要改善的草稿代码而自责， 而是对那些代
 码下手。
 
 ## **变量**
+
 ### 使用有意义并且可读的变量名称
 
 **不好的：**

From b16e0e5ca0f73b8b1aaed9468c51ec9b721ad301 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 24 Feb 2017 22:45:27 +0800
Subject: [PATCH 50/54] remove english

---
 README.md | 279 ++----------------------------------------------------
 1 file changed, 10 insertions(+), 269 deletions(-)

diff --git a/README.md b/README.md
index 4b1c4e96..6c7c0210 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@
 
 还有一件事： 知道这些指南并不能马上让你成为一个更加出色的软件开发者， 并且使用它们工作多年也并
 不意味着你不再会犯错误。 每一段代码最开始都是草稿， 像湿粘土一样被打造成最终的形态。 最后当我们
-和搭档们一起审查代码时清除那些不完善之处。 不要因为最初需要改善的草稿代码而自责， 而是对那些代
+和搭档们一起审查代码时清除那些不完善之处, 不要因为最初需要改善的草稿代码而自责， 而是对那些代
 码下手。
 
 ## **变量**
@@ -67,14 +67,6 @@ getUser();
 
 ### 使用可搜索的名称
 
-We will read more code than we will ever write. It's important that the code we
-do write is readable and searchable. By *not* naming variables that end up
-being meaningful for understanding our program, we hurt our readers.
-Make your names searchable. Tools like
-[buddy.js](https://github.com/danielstjules/buddy.js) and
-[ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
-can help identify unnamed constants.
-
 我们要阅读的代码比要写的代码多得多， 所以我们写出的代码的可读性和可搜索性是很重要的。 使用没有
 意义的变量名将会导致我们的程序难于理解， 将会伤害我们的读者， 所以请使用可搜索的变量名。 类似
 [buddy.js](https://github.com/danielstjules/buddy.js) 和 [ESLint](https://github.com/eslint/eslint/blob/660e0918933e6e7fede26bc675a0763a6b357c94/docs/rules/no-magic-numbers.md)
@@ -146,8 +138,6 @@ locations.forEach((location) => {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 不添加不必要的上下文
-If your class/object name tells you something, don't repeat that in your
-variable name.
 
 如果你的类名/对象名有意义， 不要在变量名上再重复。
 
@@ -202,28 +192,13 @@ function createMicrobrewery(breweryName = 'Hipster Brew Co.') {
 
 ### 函数参数 (两个以下最理想)
 
-Limiting the amount of function parameters is incredibly important because it
-makes testing your function easier. Having more than three leads to a
-combinatorial explosion where you have to test tons of different cases with
-each separate argument.
-
 限制函数参数的个数是非常重要的， 因为这样将使你的函数容易进行测试。 一旦超过三个参数将会导致组
-合爆炸， 因为你不得不编写大量针对单个参数的测试用例。
-
-Zero arguments is the ideal case. One or two arguments is ok, and three should
-be avoided. Anything more than that should be consolidated. Usually, if you have
-more than two arguments then your function is trying to do too much. In cases
-where it's not, most of the time a higher-level object will suffice as an
-argument.
+合爆炸， 因为你不得不编写大量针对每个参数的测试用例。
 
 没有参数是最理想的， 一个或者两个参数也是可以的， 三个参数应该避免， 超过三个应该被重构。 通常，
 如果你有一个超过两个函数的参数， 那就意味着你的函数尝试做太多的事情。 如果不是， 多数情况下一个
 更高级对象可能会满足需求。
 
-Since JavaScript allows us to make objects on the fly, without a lot of class
-boilerplate, you can use an object if you are finding yourself needing a
-lot of arguments.
-
 由于 JavaScript 允许我们不定义类型/模板就可以创建对象， 当你发现你自己需要大量的参数时， 你
 可以使用一个对象。
 
@@ -253,13 +228,7 @@ function createMenu(config) {
 
 ### 函数应当只做一件事情
 
-This is by far the most important rule in software engineering. When functions
-do more than one thing, they are harder to compose, test, and reason about.
-When you can isolate a function to just one action, they can be refactored
-easily and your code will read much cleaner. If you take nothing else away from
-this guide other than this, you'll be ahead of many developers.
-
-这是软件工程中最重要的一条规则， 当函数需要做更多的事情时， 他们将会更难进行编写、 测试和推理。
+这是软件工程中最重要的一条规则， 当函数需要做更多的事情时， 它们将会更难进行编写、 测试和推理。
 当你能将一个函数隔离到只有一个动作， 他们将能够被容易的进行重构并且你的代码将会更容易阅读。 如
 果你严格遵守本指南中的这一条， 你将会领先于许多开发者。
 
@@ -317,10 +286,6 @@ addMonthToDate(1, date);
 
 ### 函数应该只有一个抽象级别
 
-When you have more than one level of abstraction your function is usually
-doing too much. Splitting up functions leads to reusability and easier
-testing.
-
 当在你的函数中有多于一个抽象级别时， 你的函数通常做了太多事情。 拆分函数将会提升重用性和测试性。
 
 **不好的：**
@@ -388,38 +353,17 @@ function parseBetterJSAlternative(code) {
 
 ### 移除冗余代码
 
-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
-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.
-
 让这个抽象正确是关键的， 这是为什么要你遵循 *Classes* 那一章的 SOLID 的原因。 不好的抽象比冗
 余代码更差， 所以要谨慎行事。 既然已经这么说了， 如果你能够做出一个好的抽象， 才去做。 不要重复
 你自己， 否则你会发现当你要修改一个东西时时刻需要修改多个地方。
@@ -530,9 +474,6 @@ createMenu(menuConfig);
 
 
 ### 不要使用标记位做为函数参数
-Flags tell your user that this function does more than one thing. Functions
-should do one thing. Split out your functions if they are following different
-code paths based on a boolean.
 
 标记位是告诉你的用户这个函数做了不只一件事情。 函数应该只做一件事情。 如果你的函数因为一个布尔值
 出现不同的代码路径， 请拆分它们。
@@ -561,28 +502,14 @@ function createTempFile(name) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 避免副作用
-A function produces a side effect if it does anything other than take a value in
-and return another value or values. A side effect could be writing to a file,
-modifying some global variable, or accidentally wiring all your money to a
-stranger.
 
 如果一个函数做了除接受一个值然后返回一个值或多个值之外的任何事情， 它将会产生副作用， 它可能是
 写入一个文件， 修改一个全局变量， 或者意外的把你所有的钱连接到一个陌生人那里。
 
-Now, you do need to have side effects in a program on occasion. Like the previous
-example, you might need to write to a file. What you want to do is to
-centralize where you are doing this. Don't have several functions and classes
-that write to a particular file. Have one service that does it. One and only one.
-
 现在在你的程序中确实偶尔需要副作用， 就像上面的代码， 你也许需要写入到一个文件， 你需要做的是集
 中化你要做的事情， 不要让多个函数或者类写入一个特定的文件， 用一个服务来实现它， 一个并且只有一
 个。
 
-The main point is to avoid common pitfalls like sharing state between objects
-without any structure, using mutable data types that can be written to by anything,
-and not centralizing where your side effects occur. If you can do this, you will
-be happier than the vast majority of other programmers.
-
 重点是避免这些常见的易犯的错误， 比如在对象之间共享状态而不使用任何结构， 使用任何地方都可以写入
 的可变的数据类型， 没有集中化导致副作用。 如果你能做到这些， 那么你将会比其它的码农大军更加幸福。
 
@@ -619,15 +546,6 @@ console.log(newName); // ['Ryan', 'McDermott'];
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 不要写入全局函数
-Polluting globals is a bad practice in JavaScript because you could clash with another
-library and the user of your API would be none-the-wiser until they get an
-exception in production. Let's think about an example: what if you wanted to
-extend JavaScript's native Array method to have a `diff` method that could
-show the difference between two arrays? You could write your new function
-to the `Array.prototype`, but it could clash with another library that tried
-to do the same thing. What if that other library was just using `diff` to find
-the difference between the first and last elements of an array? This is why it
-would be much better to just use ES2015/ES6 classes and simply extend the `Array` global.
 
 污染全局在 JavaScript 中是一个不好的做法， 因为你可能会和另外一个类库冲突， 你的 API 的用户
 可能不够聪明， 直到他们得到在生产环境得到一个异常。 让我们来考虑这样一个例子： 假设你要扩展
@@ -656,9 +574,6 @@ class SuperArray extends Array {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 函数式编程优于指令式编程
-JavaScript isn't a functional language in the way that Haskell is, but it has
-a functional flavor to it. Functional languages are cleaner and easier to test.
-Favor this style of programming when you can.
 
 JavaScript 不是 Haskell 那种方式的函数式语言， 但是它有它的函数式风格。 函数式语言更加简洁
 并且更容易进行测试， 当你可以使用函数式编程风格时请尽情使用。
@@ -758,15 +673,7 @@ if (isDOMNodePresent(node)) {
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### 避免条件
-This seems like an impossible task. Upon first hearing this, most people say,
-"how am I supposed to do anything without an `if` statement?" The answer is that
-you can use polymorphism to achieve the same task in many cases. The second
-question is usually, "well that's great but why would I want to do that?" The
-answer is a previous clean code concept we learned: a function should only do
-one thing. When you have classes and functions that have `if` statements, you
-are telling your user that your function does more than one thing. Remember,
-just do one thing.
+### 避免条件语句
 
 这看起来似乎是一个不可能的任务。 第一次听到这个时， 多数人会说： “没有 `if` 语句还能期望我干
 啥呢”， 答案是多数情况下你可以使用多态来完成同样的任务。 第二个问题通常是 “好了， 那么做很棒，
@@ -821,10 +728,6 @@ class Cessna extends Airplane {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 避免类型检查 (part 1)
-JavaScript is untyped, which means your functions can take any type of argument.
-Sometimes you are bitten by this freedom and it becomes tempting to do
-type-checking in your functions. There are many ways to avoid having to do this.
-The first thing to consider is consistent APIs.
 
 JavaScript 是无类型的， 这意味着你的函数能接受任何类型的参数。 但是有时又会被这种自由咬伤，
 于是又尝试在你的函数中做类型检查。 有很多种方式来避免这个， 第一个要考虑的是一致的 API 。
@@ -849,15 +752,6 @@ function travelToTexas(vehicle) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 避免类型检查 (part 2)
-If you are working with basic primitive values like strings, integers, and arrays,
-and you can't use polymorphism but you still feel the need to type-check,
-you should consider using TypeScript. It is an excellent alternative to normal
-JavaScript, as it provides you with static typing on top of standard JavaScript
-syntax. The problem with manually type-checking normal JavaScript is that
-doing it well requires so much extra verbiage that the faux "type-safety" you get
-doesn't make up for the lost readability. Keep your JavaScript clean, write
-good tests, and have good code reviews. Otherwise, do all of that but with
-TypeScript (which, like I said, is a great alternative!).
 
 如果你使用原始的字符串、 整数和数组， 并且你不能使用多态， 但是你依然感觉到有类型检查的需要，
 你应该考虑使用 TypeScript 。 它是一个常规 JavaScript 的优秀的替代品， 因为它在标准的 JavaScript
@@ -886,11 +780,6 @@ function combine(val1, val2) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 不要过度优化
-Modern browsers do a lot of optimization under-the-hood at runtime. A lot of
-times, if you are optimizing then you are just wasting your time. [There are good
-resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)
-for seeing where optimization is lacking. Target those in the meantime, until
-they are fixed if they can be.
 
 现代化浏览器运行时在幕后做大量的优化， 在大多数的时间， 做优化就是在浪费你的时间。 [这些是好的
 资源](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers)， 用来
@@ -917,9 +806,6 @@ for (let i = 0; i < list.length; i++) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 移除僵尸代码
-Dead code is just as bad as duplicate code. There's no reason to keep it in
-your codebase. If it's not being called, get rid of it! It will still be safe
-in your version history if you still need it.
 
 僵死代码和冗余代码同样糟糕。 没有理由在代码库中保存它。 如果它不会被调用， 就删掉它。 当你需要
 它时， 它依然保存在版本历史记录中。
@@ -951,26 +837,13 @@ inventoryTracker('apples', req, 'www.inventory-awesome.io');
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **对象和数据结构**
+
 ### 使用 getters 和 setters
-JavaScript doesn't have interfaces or types so it is very hard to enforce this
-pattern, because we don't have keywords like `public` and `private`. As it is,
-using getters and setters to access data on objects is far better than simply
-looking for a property on an object. "Why?" you might ask. Well, here's an
-unorganized list of reasons why:
 
 JavaScript 没有接口或类型， 所以坚持这个模式是非常困难的， 因为我们没有 `public` 和 `private`
 关键字。 正因为如此， 使用 getters 和 setters 来访问对象上的数据比简单的在一个对象上查找属性
 要好得多。 “为什么？” 你可能会问， 好吧， 原因请看下面的列表：
 
-* When you want to do more beyond getting an object property, you don't have
-to look up and change every accessor in your codebase.
-* Makes adding validation simple when doing a `set`.
-* Encapsulates the internal representation.
-* Easy to add logging and error handling when getting and setting.
-* Inheriting this class, you can override default functionality.
-* You can lazy load your object's properties, let's say getting it from a
-server.
-
 * 当你想在获取一个对象属性的背后做更多的事情时， 你不需要在代码库中查找和修改每一处访问；
 * 使用 `set` 可以让添加验证变得容易；
 * 封装内部实现；
@@ -1064,11 +937,8 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 
 
 ## **类**
+
 ### ES2015/ES6 类优先与 ES5 纯函数
-It's very difficult to get readable class inheritance, construction, and method
-definitions for classical ES5 classes. If you need inheritance (and be aware
-that you might not), then prefer classes. However, prefer small functions over
-classes until you find yourself needing larger and more complex objects.
 
 很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
 要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
@@ -1144,11 +1014,6 @@ class Human extends Mammal {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 使用方法链
-This pattern is very useful in JavaScript and you see it in many libraries such
-as jQuery and Lodash. It allows your code to be expressive, and less verbose.
-For that reason, I say, use method chaining and take a look at how clean your code
-will be. In your class functions, simply return `this` at the end of every function,
-and you can chain further class methods onto it.
 
 这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
 它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
@@ -1231,12 +1096,6 @@ const car = new Car()
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 组合优先于继承
-As stated famously in [*Design Patterns*](https://en.wikipedia.org/wiki/Design_Patterns) by the Gang of Four,
-you should prefer composition over inheritance where you can. There are lots of
-good reasons to use inheritance and lots of good reasons to use composition.
-The main point for this maxim is that if your mind instinctively goes for
-inheritance, try to think if composition could model your problem better. In some
-cases it can.
 
 正如[*设计模式四人帮*](https://en.wikipedia.org/wiki/Design_Patterns)所述， 如果可能，
 你应该优先使用组合而不是继承。 有许多好的理由去使用继承， 也有许多好的理由去使用组合。这个格言
@@ -1250,13 +1109,6 @@ makes more sense than composition:
 那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
 明什么时候继承比组合更好用：
 
-1. Your inheritance represents an "is-a" relationship and not a "has-a"
-relationship (Human->Animal vs. User->UserDetails).
-2. You can reuse code from the base classes (Humans can move like all animals).
-3. You want to make global changes to derived classes by changing a base class.
-(Change the caloric expenditure of all animals when they move).
-
-
 1. 你的继承表示"是一个"的关系而不是"有一个"的关系（人类->动物 vs 用户->用户详情）；
 2. 你可以重用来自基类的代码（人可以像所有动物一样行动）；
 3. 你想通过基类对子类进行全局的修改（改变所有动物行动时的热量消耗）；
@@ -1272,7 +1124,6 @@ class Employee {
   // ...
 }
 
-// Bad because Employees "have" tax data. EmployeeTaxData is not a type of Employee
 // 不好是因为雇员“有”税率数据， EmployeeTaxData 不是一个 Employee 类型。
 class EmployeeTaxData extends Employee {
   constructor(ssn, salary) {
@@ -1311,15 +1162,8 @@ class Employee {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **SOLID**
+
 ### 单一职责原则 (SRP)
-As stated in Clean Code, "There should never be more than one reason for a class
-to change". It's tempting to jam-pack a class with a lot of functionality, like
-when you can only take one suitcase on your flight. The issue with this is
-that your class won't be conceptually cohesive and it will give it many reasons
-to change. Minimizing the amount of times you need to change a class is important.
-It's important because if too much functionality is in one class and you modify a piece of it,
-it can be difficult to understand how that will affect other dependent modules in
-your codebase.
 
 正如代码整洁之道所述， “永远不要有超过一个理由来修改一个类”。 给一个类塞满许多功能， 就像你在航
 班上只能带一个行李箱一样， 这样做的问题你的类不会有理想的内聚性， 将会有太多的理由来对它进行修改。
@@ -1374,10 +1218,6 @@ class UserSettings {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 开闭原则 (OCP)
-As stated by Bertrand Meyer, "software entities (classes, modules, functions,
-etc.) should be open for extension, but closed for modification." What does that
-mean though? This principle basically states that you should allow users to
-add new functionalities without changing existing code.
 
 Bertrand Meyer 说过， “软件实体 (类， 模块， 函数等) 应该为扩展开放， 但是为修改关闭。” 这
 是什么意思呢？ 这个原则基本上说明了你应该允许用户添加功能而不必修改现有的代码。
@@ -1464,23 +1304,11 @@ class HttpRequester {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 里氏代换原则 (LSP)
-This is a scary term for a very simple concept. It's formally defined as "If S
-is a subtype of T, then objects of type T may be replaced with objects of type S
-(i.e., objects of type S may substitute objects of type T) without altering any
-of the desirable properties of that program (correctness, task performed,
-etc.)." That's an even scarier definition.
 
 这是针对一个非常简单的里面的一个恐怖意图， 它的正式定义是： “如果 S 是 T 的一个子类型， 那么类
 型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）儿不需
 要修改目标程序的期望性质 （正确性、 任务执行性等）。” 这甚至是个恐怖的定义。
 
-The best explanation for this is if you have a parent class and a child class,
-then the base class and child class can be used interchangeably without getting
-incorrect results. This might still be confusing, so let's take a look at the
-classic Square-Rectangle example. Mathematically, a square is a rectangle, but
-if you model it using the "is-a" relationship via inheritance, you quickly
-get into trouble.
-
 最好的解释是， 如果你又一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
 能还有有些疑惑， 让我们来看一下这个经典的正方形与矩形的例子。 从数学上说， 一个正方形是一个矩形，
 但是你用 "is-a" 的关系用继承来实现， 你将很快遇到麻烦。
@@ -1587,25 +1415,13 @@ renderLargeShapes(shapes);
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 接口隔离原则 (ISP)
-JavaScript doesn't have interfaces so this principle doesn't apply as strictly
-as others. However, it's important and relevant even with JavaScript's lack of
-type system.
 
 JavaScript 没有接口， 所以这个原则不想其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
 型的语言来说， 它依然是重要并且有意义的。
 
-ISP states that "Clients should not be forced to depend upon interfaces that
-they do not use." Interfaces are implicit contracts in JavaScript because of
-duck typing.
-
 接口隔离原则说的是 “客户端不应该强制依赖他们不需要的接口。” 在 JavaScript 这种弱类型语言中，
 接口是隐式的契约。
 
-A good example to look at that demonstrates this principle in JavaScript is for
-classes that require large settings objects. Not requiring clients to setup
-huge amounts of options is beneficial, because most of the time they won't need
-all of the settings. Making them optional helps prevent having a "fat interface".
-
 在 JavaScript 中能比较好的说明这个原则的是一个类需要一个巨大的配置对象。 不需要客户端去设置大
 量的选项是有益的， 因为多数情况下他们不需要全部的设置。 让它们变成可选的有助于防止出现一个“胖接
 口”。
@@ -1671,35 +1487,17 @@ const $ = new DOMTraverser({
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 依赖反转原则 (DIP)
-This principle states two essential things:
-1. High-level modules should not depend on low-level modules. Both should
-depend on abstractions.
-2. Abstractions should not depend upon details. Details should depend on
-abstractions.
 
 这个原则阐述了两个重要的事情：
+
 1. 高级模块不应该依赖于低级模块， 两者都应该依赖与抽象；
 2. 抽象不应当依赖于具体实现， 具体实现应当依赖于抽象。
 
-This can be hard to understand at first, but if you've worked with Angular.js,
-you've seen an implementation of this principle in the form of Dependency
-Injection (DI). While they are not identical concepts, DIP keeps high-level
-modules from knowing the details of its low-level modules and setting them up.
-It can accomplish this through DI. A huge benefit of this is that it reduces
-the coupling between modules. Coupling is a very bad development pattern because
-it makes your code hard to refactor.
-
 这个一开始会很难理解， 但是如果你使用过 Angular.js ， 你应该已经看到过通过依赖注入来实现的这
 个原则， 虽然他们不是相同的概念， 依赖反转原则让高级模块远离低级模块的细节和创建， 可以通过 DI
 来实现。 这样做的巨大益处是降低模块间的耦合。 耦合是一个非常糟糕的开发模式， 因为会导致代码难于
 重构。
 
-As stated previously, JavaScript doesn't have interfaces so the abstractions
-that are depended upon are implicit contracts. That is to say, the methods
-and properties that an object/class exposes to another object/class. In the
-example below, the implicit contract is that any Request module for an
-`InventoryTracker` will have a `requestItems` method.
-
 如上所述， JavaScript 没有接口， 所以被依赖的抽象是隐式契约。 也就是说， 一个对象/类的方法和
 属性直接暴露给另外一个对象/类。 在下面的例子中， 任何一个 Request 模块的隐式契约 `InventoryTracker`
 将有一个 `requestItems` 方法。
@@ -1720,8 +1518,6 @@ class InventoryTracker {
   constructor(items) {
     this.items = items;
 
-    // BAD: We have created a dependency on a specific request implementation.
-    // We should just have requestItems depend on a request method: `request`
     // 不好的： 我们已经创建了一个对请求的具体实现的依赖， 我们只有一个 requestItems 方法依
     // 赖一个请求方法 'request'
     this.requester = new InventoryRequester();
@@ -1773,8 +1569,6 @@ class InventoryRequesterV2 {
   }
 }
 
-// By constructing our dependencies externally and injecting them, we can easily
-// substitute our request module for a fancy new one that uses WebSockets.
 // 通过外部创建依赖项并将它们注入， 我们可以轻松的用一个崭新的使用 WebSockets 的请求模块进行
 // 替换。
 const inventoryTracker = new InventoryTracker(['apples', 'bananas'], new InventoryRequesterV2());
@@ -1783,26 +1577,11 @@ inventoryTracker.requestItems();
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **测试**
-Testing is more important than shipping. If you have no tests or an
-inadequate amount, then every time you ship code you won't be sure that you
-didn't break anything. Deciding on what constitutes an adequate amount is up
-to your team, but having 100% coverage (all statements and branches) is how
-you achieve very high confidence and developer peace of mind. This means that
-in addition to having a great testing framework, you also need to use a
-[good coverage tool](http://gotwarlost.github.io/istanbul/).
 
 测试比发布更加重要。 如果你没有测试或者测试不够充分， 每次发布时你就不能确认没有破坏任何事情。
 测试的量由你的团队决定， 但是拥有 100% 的覆盖率(包括所有的语句和分支)是你为什么能达到高度自信
 和内心的平静。 这意味着需要一个额外的伟大的测试框架， 也需要一个好的[覆盖率工具](http://gotwarlost.github.io/istanbul/)。
 
-There's no excuse to not write tests. There's [plenty of good JS test frameworks]
-(http://jstherightway.org/#testing-tools), so find one that your team prefers.
-When you find one that works for your team, then aim to always write tests
-for every new feature/module you introduce. If your preferred method is
-Test Driven Development (TDD), that is great, but the main point is to just
-make sure you are reaching your coverage goals before launching any feature,
-or refactoring an existing one.
-
 没有理由不写测试。 这里有[大量的优秀的 JS 测试框架](http://jstherightway.org/#testing-tools)，
 选一个适合你的团队的即可。 当为团队选择了测试框架之后， 接下来的目标是为生产的每一个新的功能／模
 块编写测试。 如果你倾向于测试驱动开发(TDD)， 那就太棒了， 但是要点是确认你在上线任何功能或者重
@@ -1860,9 +1639,8 @@ describe('MakeMomentJSGreatAgain', () => {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **并发**
+
 ### 使用 Promises, 不要使用回调
-Callbacks aren't clean, and they cause excessive amounts of nesting. With ES2015/ES6,
-Promises are a built-in global type. Use them!
 
 回调不够简洁， 因为他们会产生过多的嵌套。 在 ES2015/ES6 中， Promises 已经是内置的全局类型
 了，使用它们吧！
@@ -1902,11 +1680,6 @@ require('request-promise').get('https://en.wikipedia.org/wiki/Robert_Cecil_Marti
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### Async/Await 比 Promises 更加简洁
-Promises are a very clean alternative to callbacks, but ES2017/ES8 brings async and await
-which offer an even cleaner solution. All you need is a function that is prefixed
-in an `async` keyword, and then you can write your logic imperatively without
-a `then` chain of functions. Use this if you can take advantage of ES2017/ES8 features
-today!
 
 Promises 是回调的一个非常简洁的替代品， 但是 ES2017/ES8 带来的 async 和 await 提供了一个
 更加简洁的解决方案。 你需要的只是一个前缀为 `async` 关键字的函数， 接下来就可以不需要 `then`
@@ -1943,21 +1716,11 @@ async function getCleanCodeArticle() {
 
 
 ## **错误处理**
-Thrown errors are a good thing! They mean the runtime has successfully
-identified when something in your program has gone wrong and it's letting
-you know by stopping function execution on the current stack, killing the
-process (in Node), and notifying you in the console with a stack trace.
 
 抛出错误是一件好事情！ 他们意味着当你的程序有错时运行时可以成功确认， 并且通过停止执行当前堆栈
 上的函数来让你知道， 结束当前进程（在 Node 中）， 在控制台中用一个堆栈跟踪提示你。
 
 ### 不要忽略捕捉到的错误
-Doing nothing with a caught error doesn't give you the ability to ever fix
-or react to said error. Logging the error to the console (`console.log`)
-isn't much better as often times it can get lost in a sea of things printed
-to the console. If you wrap any bit of code in a `try/catch` it means you
-think an error may occur there and therefore you should have a plan,
-or create a code path, for when it occurs.
 
 对捕捉到的错误不做任何处理不能给你修复错误或者响应错误的能力。 向控制台记录错误 (`console.log`)
 也不怎么好， 因为往往会丢失在海量的控制台输出中。 如果你把任意一段代码用 `try/catch` 包装那就
@@ -1988,8 +1751,6 @@ try {
 ```
 
 ### 不要忽略被拒绝的 promise 
-For the same reason you shouldn't ignore caught errors
-from `try/catch`.
 
 与你不应忽略来自 `try/catch` 的错误的原因相同。
 
@@ -2023,27 +1784,15 @@ getdata()
 
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-
 ## **格式化**
-Formatting is subjective. Like many rules herein, there is no hard and fast
-rule that you must follow. The main point is DO NOT ARGUE over formatting.
-There are [tons of tools](http://standardjs.com/rules.html) to automate this.
-Use one! It's a waste of time and money for engineers to argue over formatting.
 
 格式化是主观的。 就像其它规则一样， 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论， 这
 里有[大量的工具](http://standardjs.com/rules.html)来自动格式化， 使用其中的一个即可！ 因
 为做为工程师去争论格式化就是在浪费时间和金钱。
 
-For things that don't fall under the purview of automatic formatting
-(indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
-for some guidance.
-
 针对自动格式化工具不能涵盖的问题（缩进、 制表符还是空格、 双引号还是单引号等）， 这里有一些指南。
 
 ### 使用一致的大小写
-JavaScript is untyped, so capitalization tells you a lot about your variables,
-functions, etc. These rules are subjective, so your team can choose whatever
-they want. The point is, no matter what you all choose, just be consistent.
 
 JavaScript 是无类型的， 所以大小写告诉你关于你的变量、 函数等的很多事情。 这些规则是主观的，
 所以你的团队可以选择他们想要的。 重点是， 不管你们选择了什么， 要保持一致。
@@ -2081,9 +1830,6 @@ class Alpaca {}
 
 
 ### 函数的调用方与被调用方应该靠近
-If a function calls another, keep those functions vertically close in the source
-file. Ideally, keep the caller right above the callee. We tend to read code from
-top-to-bottom, like a newspaper. Because of this, make your code read that way.
 
 如果一个函数调用另一个， 则在代码中这两个函数的竖直位置应该靠近。 理想情况下，保持被调用函数在被
 调用函数的正上方。 我们倾向于从上到下阅读代码， 就像读一章报纸。 由于这个原因， 保持你的代码可
@@ -2170,8 +1916,8 @@ review.perfReview();
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ## **评论**
+
 ### 仅仅对包含复杂业务逻辑的东西进行评论
-Comments are an apology, not a requirement. Good code *mostly* documents itself.
 
 评论是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
 
@@ -2216,7 +1962,6 @@ function hashIt(data) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 不要在代码库中保存注释掉的代码
-Version control exists for a reason. Leave old code in your history.
 
 因为有版本控制， 把旧的代码留在历史记录即可。
 
@@ -2235,8 +1980,6 @@ doStuff();
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 不要有日志式的评论
-Remember, use version control! There's no need for dead code, commented code,
-and especially journal comments. Use `git log` to get history!
 
 记住， 使用版本控制！ 不需要僵尸代码， 注释调的代码， 尤其是日志式的评论。 使用 `git log` 来
 获取历史记录。
@@ -2263,8 +2006,6 @@ function combine(a, b) {
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
 ### 避免占位符
-They usually just add noise. Let the functions and variable names along with the
-proper indentation and formatting give the visual structure to your code.
 
 它们仅仅添加了干扰。 让函数和变量名称与合适的缩进和格式化为你的代码提供视觉结构。
 

From abab279485827119afa3ecc1ae22118b3701c0f3 Mon Sep 17 00:00:00 2001
From: gihann <webdev40great@gmail.com>
Date: Wed, 12 Sep 2018 14:11:42 +0800
Subject: [PATCH 51/54] =?UTF-8?q?fix:=20=E6=9B=B4=E6=AD=A3=E5=B7=AE?=
 =?UTF-8?q?=E5=88=AB=E5=AD=97?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6c7c0210..addeba68 100644
--- a/README.md
+++ b/README.md
@@ -1170,7 +1170,7 @@ class Employee {
 最小化需要修改一个类的次数时很重要的， 因为如果一个类拥有太多的功能， 一旦你修改它的一小部分，
 将会很难弄清楚会对代码库中的其它模块造成什么影响。
 
-**好的：**
+**不好的：**
 ```javascript
 class UserSettings {
   constructor(user) {

From 32173a6b312ce8d4e56cc0a3a092b28299e0f7f3 Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Sun, 17 Feb 2019 16:55:14 +0800
Subject: [PATCH 52/54] fix typo

---
 README.md | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/README.md b/README.md
index addeba68..c1325515 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@
   8. [并发](#并发)
   9. [错误处理](#错误处理)
   10. [格式化](#格式化)
-  11. [评论](#评论)
+  11. [注释](#注释)
   12. [Translation](#translation)
 
 ## 简介
@@ -941,7 +941,7 @@ console.log(`Employee name: ${employee.getName()}`); // Employee name: John Doe
 ### ES2015/ES6 类优先与 ES5 纯函数
 
 很难为经典的 ES5 类创建可读的的继承、 构造和方法定义。 如果你需要继承（并且感到奇怪为啥你不需
-要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 知道你发现你需要更大并且更复杂的
+要）， 则优先用 ES2015/ES6的类。 不过， 短小的函数优先于类， 直到你发现你需要更大并且更复杂的
 对象。
 
 **不好的：**
@@ -983,7 +983,7 @@ Human.prototype.constructor = Human;
 Human.prototype.speak = function speak() {};
 ```
 
-**好的**
+**好的：**
 ```javascript
 class Animal {
   constructor(age) {
@@ -1016,7 +1016,7 @@ class Human extends Mammal {
 ### 使用方法链
 
 这个模式在 JavaScript 中是非常有用的， 并且你可以在许多类库比如 jQuery 和 Lodash 中见到。
-它允许你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
+它使你的代码变得富有表现力， 并减少啰嗦。 因为这个原因， 我说， 使用方法链然后再看看你的代码
 会变得多么简洁。 在你的类／方法中， 简单的在每个方法的最后返回 `this` ， 然后你就能把这个类的
 其它方法链在一起。
 
@@ -1102,10 +1102,6 @@ const car = new Car()
 的重点是， 如果你本能的观点是继承， 那么请想一下组合能否更好的为你的问题建模。 很多情况下它真的
 可以。
 
-You might be wondering then, "when should I use inheritance?" It
-depends on your problem at hand, but this is a decent list of when inheritance
-makes more sense than composition:
-
 那么你也许会这样想， “我什么时候改使用继承？” 这取决于你手上的问题， 不过这儿有一个像样的列表说
 明什么时候继承比组合更好用：
 
@@ -1915,11 +1911,11 @@ review.perfReview();
 
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-## **评论**
+## **注释**
 
-### 仅仅对包含复杂业务逻辑的东西进行评论
+### 仅仅对包含复杂业务逻辑的东西进行注释
 
-评论是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
+注释是代码的辩解， 不是要求。 多数情况下， 好的代码就是文档。
 
 **不好的：**
 ```javascript
@@ -1979,9 +1975,9 @@ doStuff();
 ```
 **[⬆ 返回顶部](#代码整洁的-javascript)**
 
-### 不要有日志式的评论
+### 不要有日志式的注释
 
-记住， 使用版本控制！ 不需要僵尸代码， 注释调的代码， 尤其是日志式的评论。 使用 `git log` 来
+记住， 使用版本控制！ 不需要僵尸代码， 注释掉的代码， 尤其是日志式的注释。 使用 `git log` 来
 获取历史记录。
 
 **不好的：**

From 95a637c397abe277dbbdaaedfb4fc6019e46f94d Mon Sep 17 00:00:00 2001
From: beginor <beginor@qq.com>
Date: Fri, 11 Dec 2020 09:05:21 +0800
Subject: [PATCH 53/54] Create FUNDING.yml

---
 .github/FUNDING.yml | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 .github/FUNDING.yml

diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
new file mode 100644
index 00000000..219c0610
--- /dev/null
+++ b/.github/FUNDING.yml
@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: ['paypal.me/beginor']

From cc1efb1be46d0669ca7570e15096ed5b0882d979 Mon Sep 17 00:00:00 2001
From: melon95 <lijunwork95@gmail.com>
Date: Fri, 7 Jan 2022 21:27:35 +0800
Subject: [PATCH 54/54] =?UTF-8?q?fixed:=20=E9=94=99=E5=88=AB=E5=AD=97?=
 =?UTF-8?q?=E4=BF=AE=E5=A4=8D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index c1325515..4b0f987d 100644
--- a/README.md
+++ b/README.md
@@ -1302,10 +1302,10 @@ class HttpRequester {
 ### 里氏代换原则 (LSP)
 
 这是针对一个非常简单的里面的一个恐怖意图， 它的正式定义是： “如果 S 是 T 的一个子类型， 那么类
-型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）儿不需
+型为 T 的对象可以被类型为 S 的对象替换（例如， 类型为 S 的对象可作为类型为 T 的替代品）而不需
 要修改目标程序的期望性质 （正确性、 任务执行性等）。” 这甚至是个恐怖的定义。
 
-最好的解释是， 如果你又一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
+最好的解释是， 如果你有一个基类和一个子类， 那个基类和字类可以互换而不会产生不正确的结果。 这可
 能还有有些疑惑， 让我们来看一下这个经典的正方形与矩形的例子。 从数学上说， 一个正方形是一个矩形，
 但是你用 "is-a" 的关系用继承来实现， 你将很快遇到麻烦。
 
@@ -1412,7 +1412,7 @@ renderLargeShapes(shapes);
 
 ### 接口隔离原则 (ISP)
 
-JavaScript 没有接口， 所以这个原则不想其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
+JavaScript 没有接口， 所以这个原则不像其它语言那么严格。 不过， 对于 JavaScript 这种缺少类
 型的语言来说， 它依然是重要并且有意义的。
 
 接口隔离原则说的是 “客户端不应该强制依赖他们不需要的接口。” 在 JavaScript 这种弱类型语言中，