Page 1
https://en.wikipedia.org/wiki/List_of_eponymous_laws
https://en.wikipedia.org/wiki/List_of_eponymous_laws#NewtonSword
| Law | Summary | Common Relevance |
|---|---|---|
| Parkinson's Law | Work expands to fill the available time. | Scheduling |
| Betteridge's law of headlines | Any headline that ends in a question mark can be answered by the word no. | headlines |
| 1. Murphy's Law | Anything that can go wrong eventually will. | Reliability, operations |
| 2. Brooks's Law | Adding people to a late software project makes it later. | Project management |
| 3. Conway's Law | Systems mirror the communication structure of their organizations. | Architecture |
| 5. Hofstadter's Law | Everything takes longer than expected, even accounting for the law. | Estimation |
| 6. Postel's Law | Be conservative in what you send, liberal in what you accept. | Internet protocols |
| 7. Linus's Law | Given enough eyeballs, all bugs are shallow. | Open source |
| 8. Metcalfe's Law | A network's value grows roughly with the square of its users. | Social networks |
| 9. Moore's Law | Computing power tends to grow exponentially over time. | Hardware |
| 10. Wirth's Law | Software becomes slower faster than hardware becomes faster. | Performance |
| 11. Amdahl's Law | Parallel speedup is limited by the serial portion. | Concurrency |
| 12. Little's Law | Average items in a system equal arrival rate × average time. | Distributed systems |
| 13. Gall's Law | Complex systems that work evolve from simple systems that work. | Architecture |
| 14. Tesler's Law | Complexity cannot be eliminated, only shifted. | UX, APIs |
| 15. Goodhart's Law | When a measure becomes a target, it ceases to be a good measure. | KPIs, ML |
| 16. Occam's Razor | Prefer the simplest adequate explanation. | Debugging |
| 17. Hanlon's Razor | Don't attribute to malice what can be explained by incompetence. | Incident analysis |
| 18. Pareto Principle | Roughly 80% of effects come from 20% of causes. | Optimization |
| 19. Knuth's Optimization Principle | Premature optimization is the root of much evil. | Performance engineering |
| 20. Lehman's Laws | Successful software continually evolves and grows more complex. | Maintenance |
| 21. Zawinski's Law | Every program attempts to expand until it can read email. | Feature creep |
| 22. Hyrum's Law | Every observable behavior of an API will eventually have users depending on it. | API design |
| 23. Cunningham's Law | The best way to get the right answer online is to post the wrong one. | Online communities |
| 24. Godwin's Law | As online discussion grows longer, comparisons to Nazis become inevitable. | Forums |
| 25. Brandolini's Law | Refuting misinformation requires far more effort than producing it. | Social media |
| 26. Beck's Law | Simplicity is often the most scalable solution. | Software design |
| 27. Ninety–Ninety Rule | The last 10% of a project takes another 90% of the time. | Project estimation |
| 28. Sturgeon's Law | Ninety percent of everything is crud. | Software quality |
| 29. Bell's Law | New computer classes emerge as technology advances. | Computing history |
| 30. Shirky Principle | Institutions try to preserve the problem they solve. | Platform governance |