Re:Chesterton’s Fence: A Lesson in Second Order Thinking
by humanrebar on Tuesday March 10, 2020 @09:24PM
(#22542001)
It's worth mentioning that cargo culting and arbitrary decision-making aren't necessarily bad from the perspective of the Chesteron's Fence thought experiment.
It may not matter if people who left the fence alone even knew why they were doing it. What matters is whether the fence serves an important purpose. Of course, there is wisdom in finding out exact reasons, but sometimes the reasons aren't consciously chosen. There are such things as emergent and unintended benefits.
Re:Chesterton’s Fence: A Lesson in Second Order Thinking
by uk_programmer on Wednesday March 11, 2020 @10:10AM
(#22545963)
Cargo-culting can sometimes be okay. I normally have to work on large legacy code bases and sometimes it is simply better to try to copy something similar in the codebase in terms of functionality and try to follow the structure of what went before. Without documentation it is sometimes the only way to udnerstand the codebase. Especially when people have (ab)used reflection or dependency injection.
We use it for differentiating Chesterton's Fence from cargo culting and arbitrary decisions.
You go back and find out from context that code was there to fix a bug or implement a requirement that no longer exists, you remove the code. You find out the person just liked to write code this way, you remove the code.
You find out that it was to solve a problem on FreeBSD or old Docker versions or for your biggest customer, you leave the code, or reimplement the fix.
Nobody will remember why they did something, but you can often figure it out from the shape of the commit and its siblings.