April 21, 2026
When coding meets the law
Laws of Software Engineering
Programmers say the real law is: chaos always wins
TLDR: A website tried to crown 56 “laws” that supposedly govern how software and teams behave, from creeping complexity to bad management. Developers reacted by mocking the list as half real physics, half social pressure, arguing over missing rules, and insisting you should trust real practitioners and textbooks instead.
A new site tried to lay down the 56 “Laws of Software Engineering” — basically a holy rulebook for how code and teams should work — and developers immediately showed up to say, “Yeah, some of these are gravity, the rest are just social shame weapons.” One top commenter split the list in two: unbreakable forces like growing complexity, and “laws” that only work because your coworkers yell at you, like the Boy Scout rule of leaving code cleaner than you found it.
Others dismissed the page as a pretty poster of fortune-cookie quotes. One reader waved it off as a “visual list of well-known aphorisms,” then immediately started name-dropping books and sharing a reading list, flexing their bookshelf like it was a gym selfie. Another fired back that key rules were missing, like Boyd’s idea that quick repetition beats endless planning — the classic internet move: “Cool list, here’s what you forgot.”
The real nerd fight kicked in when people argued over how we deal with complexity. One commenter dropped a math-style formula to say that hiding mess in stable parts of the system is as good as deleting it, while another got blunt: forget cute laws, just learn from people who actually build stuff and read real textbooks. Beneath the jokes and snark, the crowd agreed on one thing: in software, chaos is inevitable — the only argument is which guru you quote while it burns.
Key Points
- •The page curates 56 software engineering laws as clickable cards with brief explanations.
- •Content is organized by categories such as Architecture, Teams, Design, Quality, and Planning.
- •Highlighted principles include Conway’s Law, CAP Theorem, Law of Leaky Abstractions, and Tesler’s Law.
- •Team dynamics and management concepts like Brooks’s Law, Bus Factor, and Peter Principle are included.
- •Each law has a concise summary and links to detailed pages and a related book.