Merge pull request #8 from dwmkerr/feat/hofstadters-law

feat: add hofstadter's law. closes #7.
This commit is contained in:
Dave Kerr
2018-10-03 21:12:36 +08:00
committed by GitHub

View File

@@ -8,6 +8,7 @@ Laws, Theories, Patterns and Ideas that all developers should know about!
* [Introduction](#introduction) * [Introduction](#introduction)
* [The Laws](#the-laws) * [The Laws](#the-laws)
* [⭐⭐ Conway's Law](#-conways-law) * [⭐⭐ Conway's Law](#-conways-law)
* [⭐ Hofstadter's Law](#-hofstadters-law)
* [⭐⭐⭐ The Unix Philosophy](#-the-unix-philosophy) * [⭐⭐⭐ The Unix Philosophy](#-the-unix-philosophy)
* [⭐The Spotify Model](#the-spotify-model) * [⭐The Spotify Model](#the-spotify-model)
@@ -32,6 +33,14 @@ This law suggests that the technical boundaries of a system will reflect the str
See also: 'The Spotify Model'. See also: 'The Spotify Model'.
### ⭐ Hofstadter's Law
[Hofstadter's Law on Wikipedia](https://en.wikipedia.org/wiki/Hofstadter%27s_law)
> It always takes longer than you expect, even when you take into account Hofstadter's Law.
You might hear this law referred to when looking at estimates for how long something will take. It seems a truism in software development that we tend to not be very good at accurately estimating how long something will take to deliver.
### ⭐⭐⭐ The Unix Philosophy ### ⭐⭐⭐ The Unix Philosophy
[The Unix Philosophy on Wikipedia](https://en.wikipedia.org/wiki/Unix_philosophy) [The Unix Philosophy on Wikipedia](https://en.wikipedia.org/wiki/Unix_philosophy)