summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Kerr <dwmkerr@gmail.com>2019-10-07 14:27:50 +0800
committerDave Kerr <dwmkerr@gmail.com>2019-10-07 14:27:50 +0800
commit9bfe7007df2a3706a290b3e1982c793f00a55e93 (patch)
tree9456126b0970a569030cb6d6316a3de1740a17c5
parent1137e9723a1f56fd7c844c23759b73cb6d8bf633 (diff)
chore: tweak wording of KISS slightly
-rw-r--r--README.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/README.md b/README.md
index b956929..3e0a783 100644
--- a/README.md
+++ b/README.md
@@ -48,7 +48,7 @@ Laws, Theories, Principles and Patterns that developers will find useful.
* [The Interface Segregation Principle](#the-interface-segregation-principle)
* [The Dependency Inversion Principle](#the-dependency-inversion-principle)
* [The DRY Principle](#the-dry-principle)
- * [The KISS Principle](#the-kiss-principle)
+ * [The KISS principle](#the-kiss-principle)
* [YAGNI](#yagni)
* [Reading List](#reading-list)
* [TODO](#todo)
@@ -566,9 +566,11 @@ See also:
[KISS on Wikipedia](https://en.wikipedia.org/wiki/KISS_principle)
-> The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided.
+> Keep it simple, stupid
-KISS, an acronym for "keep it simple, stupid", is a design principle noted by the U.S. Navy in 1960. The phrase has been associated with aircraft engineer Kelly Johnson. The principle is best exemplified by the story of Johnson handing a team of design engineers a handful of tools, with the challenge that the jet aircraft they were designing must be repairable by an average mechanic in the field under combat conditions with only these tools. Hence, the "stupid" refers to the relationship between the way things break and the sophistication available to repair them.
+The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided. Originating in the U.S. Navy in 1960, the phrase has been associated with aircraft engineer Kelly Johnson.
+
+The principle is best exemplified by the story of Johnson handing a team of design engineers a handful of tools, with the challenge that the jet aircraft they were designing must be repairable by an average mechanic in the field under combat conditions with only these tools. Hence, the "stupid" refers to the relationship between the way things break and the sophistication of the tools available to repair them, not the capabilities of the engineers themselves.
See also: