mirror of
https://github.com/dwmkerr/hacker-laws.git
synced 2025-12-17 20:55:02 +01:00
Add Hutber's Law
It's an awfully cynical one, but it's a failure I've seen in the wild more times than I'd like to count.
This commit is contained in:
@@ -10,6 +10,7 @@ Laws, Theories, Principles and Patterns that developers will find useful.
|
||||
* [Brooks's Law](#brookss-law)
|
||||
* [Conway's Law](#conways-law)
|
||||
* [Hofstadter's Law](#hofstadters-law)
|
||||
* [Hutber's Law](#hutbers-law)
|
||||
* [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)
|
||||
@@ -98,6 +99,14 @@ See also:
|
||||
|
||||
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.
|
||||
|
||||
### Hutber's Law
|
||||
|
||||
[Hutber's Law on Wikipedia](https://en.wikipedia.org/wiki/Hutber%27s_law)
|
||||
|
||||
> Improvement means deterioration.
|
||||
|
||||
This law suggests that improvements to a system will lead to deterioration in other parts, or it will hide other deterioration, leading overall to a degredation from the current state of the system. For example, a decrease in response latency for a particular end-point could cause increased throughput and capacity issues further along in a request flow, effecting an entirely different sub-system.
|
||||
|
||||
### The Hype Cycle & Amara's Law
|
||||
|
||||
[The Hype Cycle on Wikipedia](https://en.wikipedia.org/wiki/Hype_cycle)
|
||||
|
||||
Reference in New Issue
Block a user