From 93dec16bc9d2517c7de5fcc5533b124cdcae812a Mon Sep 17 00:00:00 2001 From: Dave Kerr Date: Wed, 23 Sep 2020 22:02:28 +0800 Subject: [PATCH] feat: all models are wrong Closes #263 --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 0712e22..f21e1c5 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,7 @@ Like this project? Please considering [sponsoring me](https://github.com/sponsor * [Wadler's Law](#wadlers-law) * [Wheaton's Law](#wheatons-law) * [Principles](#principles) + * [All Models Are Wrong (George Box's Law)](#all-models-are-wrong-george-boxs-law) * [Chesterson's Fence](#chestersons-fence) * [The Dead Sea Effect](#the-dead-sea-effect) * [The Dilbert Principle](#the-dilbert-principle) @@ -641,6 +642,22 @@ Coined by Wil Wheaton (Star Trek: The Next Generation, The Big Bang Theory), thi Principles are generally more likely to be guidelines relating to design. +### All Models Are Wrong (George Box's Law) + +[All Models Are Wrong](https://en.wikipedia.org/wiki/All_models_are_wrong) + +> All models are wrong, but some are useful. +> +> _George Box_ + +This principle suggests that all models of systems are flawed, but that as long as they are not _too_ flawed they may be useful. This principle has its roots in statistics but applies to scientific and computing models as well. + +A fundamental requirement of most software is to model a system of some kind. Regardless of whether the system being modeled is a computer network, a library, a graph of social connections or any other kind of system, the designer will have to decide an appropriate level of detail to model. Excessive detail may lead to too much complexity, too little detail may prevent the model from being functional. + +See also: + +- [The Law of Leaky Abstractions](#the-law-of-leaky-abstractions) + ### Chesterson's Fence [Chesterson's Fence on Wikipedia](https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence)