Comment by NoItsDanger
12 hours ago
I’ve always liked Chesterton’s Fire.
Maybe there’s a reason you’re on fire. Until you can say for sure, I will not put it out.
I will just be here roasting these marshmallows on your burning flesh. :)
12 hours ago
I’ve always liked Chesterton’s Fire.
Maybe there’s a reason you’re on fire. Until you can say for sure, I will not put it out.
I will just be here roasting these marshmallows on your burning flesh. :)
What a ridiculous misrepresentation of the principle. In fact isn't that a good illustration of the principle? The fence is just sitting there, maybe it's annoying or slows you down but it isn't actually an acute problem or an emergency. All the more reason to not just rip it out without taking the time to understand why it's there.
My version was Chesterton's Facehugger.
Something which, as soon as you discover it, you should immediately respond by trying to remove it, without asking questions about where it came from or what its purpose might be.
Do you have a real practical example of this? I have never encountered a real one that didn't turn out to be a fence in hindsight.
I have encountered many. For example if you find a password in plaintext in source control, you don't assume the person who put it there had a good reason, you assume they were deeply misguided.