Don't Move That Fence Til You Know Why It's There
summary
A practical rule from Chesterton's fence: don’t remove behavior until you can state why it exists and what your change will break. Concrete examples: the Debian OpenSSL bug results in only 1 of 65,535 SSL keys being generated, and an Anaconda/systemd interaction hinges on an ANSI escape that sets terminals to UTF‑8. Use git blame, git show and history digging to find the original reason, and write commit messages that record both what changed and why so future bisects succeed.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:33G.K. Chesterton
- 1:08The Quote
- 2:41The Context
- 5:36The Idea
- 6:44The Exomple
- 9:19The Reveal
- 10:02The Lessons
- 11:16The Corollary
- 11:59The Tools
related talks
46mGood Fences Make Good Neighbours
50mCommitter Review: An Exercise in Paranoia
27mMove Thoughtfully and build things
36mUnintended consequences of well-meaning changes
52mGood Fences Make Good Neighbours
48mGood Fences Make Good Neighbours
37mThe Hare and the Tortoise Open Source, Standards & Technical Debt
46mYour Code Base as a Crime Scene