Reasoning
Chesterton's Fence
You join a new team and inherit a release checklist. Half the steps look outdated. One line says, 'Ping Dana before Friday releases.' Dana left months ago, so you delete it. The next payday, a Friday release collides with a batch job and payouts fail. Someone says Dana used to check a map of overnight jobs and a weird legacy queue. She knew why the path bent the way it did. You saw a fence and an idle axe in your hand. You did not stop to ask who built it, or why.
People add rules, defaults, and warnings to stop specific pain. When the pain is quiet, the guard starts to look pointless. You see the cost and miss the job it was doing. Chesterton's Fence says do not scrap a thing until you can name what it was protecting and when it last mattered. This applies to speed bumps, fraud checks, weird cron jobs, and that extra approval step at work.
Therefore
Before you remove a rule, write down the job it did and how you will cover it. If you cannot say that plainly, do not touch it yet.
Chesterton, 1929
In 1929, in London, G. K. Chesterton wrote an essay in The Thing about reforms. He pictured two men who find a fence across a road. The first says, remove it. The second says, not until you tell me what it is doing. Maybe it keeps cattle out of the crops, or marks a sudden drop, or guards a buried water main. If you cannot say which, you are not ready to cut. Learn the reason, then decide. His short parable spread because people saw their own offices in it.
A small reminder, on a laptop lid or a shop wall, that the thing you plan to remove was doing a job you should name first.
$3.50
2.5 inches vinyl · weatherproof · ships in 1–3 days
Mix & save: 3 for $9 · 5 for $14 · 10 for $25· free shipping at ten
- Weatherproof vinyl
- Ships from Wayzata in 1–3 business days
- Secure checkout
If anything is wrong, we'll refund or replace it. Read the policy
