summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Kerr <dwmkerr@gmail.com>2019-05-22 23:25:50 +0800
committerGitHub <noreply@github.com>2019-05-22 23:25:50 +0800
commit814e357b97d7bc1c111c157e66fe889164806534 (patch)
tree293e6d328c6742adf3fcfa641157dca9d01ce93b
parentafbb055ea3844faccaa46d998f017c8b51589f9a (diff)
parent0c1c4fa04dce7f301b5c41c1e61ea04eba34d93b (diff)
Merge pull request #97 from rbalazs/add-pareto-principle
Pareto principle
-rw-r--r--README.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/README.md b/README.md
index fb0faa8..72faa18 100644
--- a/README.md
+++ b/README.md
@@ -16,6 +16,7 @@ Laws, Theories, Principles and Patterns that developers will find useful.
* [The Hype Cycle & Amara's Law](#the-hype-cycle--amaras-law)
* [Hyrum's Law (The Law of Implicit Interfaces)](#hyrums-law-the-law-of-implicit-interfaces)
* [Moore's Law](#moores-law)
+ * [Pareto principle](#pareto-principle)
* [Parkinson's Law](#parkinsons-law)
* [Putt's Law](#putts-law)
* [The Law of Conservation of Complexity (Tesler's Law)](#the-law-of-conservation-of-complexity-teslers-law)
@@ -166,6 +167,25 @@ See also:
Often used to illustrate the sheer speed at which semiconductor and chip technology has improved, Moore's prediction has proven to be highly accurate over from the 1970s to the late 2000s. In more recent years, the trend has changed slightly, partly due to [physical limitations on the degree to which components can be miniaturised](https://en.wikipedia.org/wiki/Quantum_tunnelling). However, advancements in parallelisation, and potentially revolutionary changes in semiconductor technology and quantum computing may mean that Moore's Law could continue to hold true for decades to come.
+### Pareto principle
+
+[Pareto principle on Wikipedia](https://en.wikipedia.org/wiki/Pareto_principle)
+
+>Most things in life are not distributed evenly.
+
+The Pareto Principle helps you realize that the majority of results come from a minority of inputs:
+ - 80% of a certain piece of software can be written in 20% of the total allocated time (conversely, the hardest 20% of the code takes 80% of the time)
+- 20% of the effort produce 80% of the result
+- 20% of the work create 80% of the revenue
+- 20% of the bugs cause 80% of the crashes
+- 20% of the features cause 80% of the usage
+
+In the 1940s American-Romanian engineer Dr. Joseph Juran, who is widely credited with being the father of quality control, [began to apply the Pareto principle to quality issues](https://en.wikipedia.org/wiki/Joseph_M._Juran).
+
+Real-world example:
+
+In 2002 Microsoft reported that by fixing the top 20% of the most-reported bugs, 80% of the related errors and crashes in windows and office would become eliminated.
+
### Parkinson's Law
[Parkinson's Law on Wikipedia](https://en.wikipedia.org/wiki/Parkinson%27s_law)