Chapter 27 — The Laws of Software Architecture, Revisited

Core ideas

a capstone. The book’s “laws”:

• First Law: Everything in software architecture is a trade-off. (Corollary: if you think you’ve found something that isn’t a trade-off, you just haven’t identified the trade-off yet.)
• Second Law: Why is more important than how.
• Third Law (2e): Most architecture decisions aren’t binary; the answer usually lies in the balance between opposing forces (i.e., it’s a spectrum, not a yes/no).
• Ties the whole book together: characteristics, styles, decisions, and soft skills are all applications of trade-off thinking, captured through the “why,” expressed as a balance.