Tradition as Inherited Hypothesis
Updated
Knowledge on this page was mainly distilled from Tradition Is Just an Inherited Hypothesis.
A tradition is an inherited hypothesis: somebody's claim, frozen into practice, that a given solution is the best available answer to a problem. The claim was probably true when they made it. Whether it is still true is a question nobody assigned to anyone.
The Life Cycle of a Tradition
Every tradition starts the same way. Someone faces a problem, solves it with the best tools their constraints allow, and the solution works. People repeat it. Repetition makes it normal. Normal makes it invisible. A generation later the problem is forgotten and the solution is still running.
Problem, solution, repetition, ritual. That is the whole life cycle.
The Courier Radio Example
When Haim owned a courier service, the de facto standard for reaching drivers on the road was the two-way radio. It solved a real problem: dispatch had no other way to communicate with a moving vehicle. The radio was the correct answer under the constraints that existed.
Then mobile phones became affordable. Better experience, less hassle, lower overall cost, for the same problem. The day that happened, the radio stopped being a solution and became a habit. Nothing about the radio announced the change. Habits never announce their own expiration.
The radio was never wrong. It was right under constraints that quietly stopped existing.
A Hypothesis, Not a Command
Seeing tradition as hypothesis does not mean discarding everything old. Some inherited decisions are still the best answers available, and the people most eager to tear them down tend to rebuild them badly. The point is that a hypothesis can advise you; it cannot command you. The inherited answer and any new candidate both have to argue from today's conditions, and neither gets grandfathered in.
A neighbor from Haim's childhood demonstrated this. Where Haim grew up, leaving the country was frowned upon as a quiet betrayal. The neighbor did not rage against the custom. He replaced the pre-decided verdict with an evaluation: staying or leaving is a personal decision based on how comfortable and advantageous life is here versus somewhere else. Weigh both honestly, then choose. He recovered the question the tradition had fossilized and re-derived the answer from current conditions. And because his evaluation had brought him back, he arrived at the same verdict the tradition demanded, reached in a way that made it his own.
A verdict you inherit belongs to the past. The same verdict, re-derived, belongs to you.
Q&A
If tradition carries compressed wisdom, why call it 'just' a hypothesis?
Calling it a hypothesis is not a demotion. It acknowledges that the wisdom is real but was generated under specific constraints. A hypothesis that has survived testing deserves respect, but it still needs to be re-tested when conditions change, because the constraints that made it wise may no longer exist.
Is this the same as saying 'we've always done it this way' is a fallacy?
'We've always done it this way' is an appeal to tradition, a recognized logical fallacy. But the hypothesis framing adds nuance: the practice may still be correct even though the argument for it is fallacious. The fix is not to discard the practice but to find a real argument for or against it based on current conditions.
How does this differ from first-principles thinking?
First-principles thinking derives answers from scratch, ignoring existing solutions. The inherited-hypothesis framing starts with the existing solution, traces the problem it solved, and then checks whether the problem and constraints still hold. It respects that inherited practice often contains knowledge nobody alive can fully articulate.
Does re-deriving every tradition create decision fatigue?
Yes, and the article acknowledges this tension directly. Traditions exist partly to save thousands of small decisions. The recommendation is not to audit everything but to audit when a constraint dies, such as when something new becomes cheap, fast, or possible for the first time. That is the trigger, not a calendar.
Can the same tradition get different verdicts in different contexts?
Absolutely. The article uses the Thursday deploy rule as an example. In a shop where rollbacks still take hours and a human, the constraint is alive and the rule is a keep. In a shop where rollback is one command, the constraint is dead and the rule is running on inertia. Same practice, opposite verdicts, because the test reads your constraints, not the practice's reputation.