Law and Engineering Are Distant Cousins
Law and Engineering: A Systems Comparison
Law and engineering are distant cousins in the family of human problem-solving. Both disciplines work with constants, variables, and rules. Both aim for predictable outcomes. Yet they diverge fundamentally in how they treat change, precedent, and innovation. Understanding this divergence reveals something important about why legal systems resist the speed of technological transformation—and what that resistance costs.
Let's start with what they share. In engineering, you have fixed constants: gravity is 9.8 m/s², materials have known tensile strengths, thermodynamic principles don't negotiate. You have variables: load, temperature, duration of stress. And you have rules—equations, design standards, safety factors—that combine constants and variables to produce a predictable result. A bridge either stands or fails based on whether the formula resolves correctly.
Law works similarly. Fixed constants exist: the Constitution, statutes, foundational principles. Variables include facts, circumstances, and the specific details of each case. Rules—procedural law, evidentiary standards, substantive legal doctrines—combine these elements to reach a judgment. A contract either binds or doesn't, depending on whether the legal formula resolves correctly.
Jurisdiction as Environment
Here's where the analogy deepens: jurisdiction is the environment that changes how the formula behaves. Just as the same bridge design performs differently at sea level versus 14,000 feet, the same legal principle produces different outcomes in different jurisdictions. A contract enforceable in New York may be unenforceable in California. The variables and rules shift; the outcome shifts with them.
The Precedent Problem
But engineering and law diverge sharply on one critical point: how they treat precedent and change. In engineering, precedent is a starting point. We study historical bridge failures, learn from them, and build better bridges. We don't replicate the Tacoma Narrows Bridge design because it collapsed; we understand why it failed and innovate beyond it.
Law, by contrast, treats precedent as binding constraint. Precedent doesn't just inform legal reasoning—it constrains it. A judge cannot simply decide that a 123-year-old rule no longer makes sense in a digital economy and abandon it. The doctrine of stare decisis—"let the decision stand"—means that past resolutions become structural features of the system itself. Courts will do it exactly like they did it 123 years ago unless a higher court explicitly overrules that precedent or the legislature changes the statute.
This creates a profound structural asymmetry. Technology moves exponentially. Legal systems move incrementally, bound by the weight of accumulated decisions. A software engineer can deploy a new version overnight. A lawyer arguing for a new interpretation of contract law must first dismantle the precedential architecture that has accumulated for decades.
Why This Matters
The profession's strength—its stability, its predictability, its resistance to whim—is also its constraint on speed.
This isn't a flaw in legal reasoning. Stability matters. Predictability protects people. You want contract law to mean the same thing today as it did last year. But it does mean that law and engineering operate on fundamentally different timescales and change mechanisms. Engineering asks: "What's the best solution now?" Law asks: "What did we decide before, and do we have sufficient reason to change it?"
The distant cousins solve problems differently. Neither approach is wrong. But understanding the difference—understanding that law is structurally resistant to innovation in ways engineering is not—is essential for anyone trying to bridge the gap between legal systems and technological change.