Scott and Scurvy (2010)
idlewords.com
Scott and Scurvy (2010)
1–7 of 7 posts
Re: Scott and Scurvy (2010)
#2A striking example of Chesterton's fence:
https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...
Re: Scott and Scurvy (2010)
#3I started taking 2,000 mg of vitamin C daily. WBC count bounced back and, after a tooth extraction, pain is gone.
Re: Scott and Scurvy (2010)
#4Re: Scott and Scurvy (2010)
#5In this, the Navy was deceived. Tests on animals would later show that fresh lime juice has a quarter of the scurvy-fighting power of fresh lemon juice. A striking example of Chesterton's fence: https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...
That's not to to say that cultural evolution doesn't happen, but the relationship between vitamin-c and scurvy just happened to be extremely hard to work out.
Re: Scott and Scurvy (2010)
#6In this, the Navy was deceived. Tests on animals would later show that fresh lime juice has a quarter of the scurvy-fighting power of fresh lemon juice. A striking example of Chesterton's fence: https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...
I suspect scurvy in particular is an unusually poor model of Chesterton's fence. There were centuries of incredibly stupid ideas before the use of lemons came along, and the benefits of lemons were not obvious, or other nations would have adopted the practice. Blindly keeping with tradition would have helped only in the switch from lemon juice to lime- indeed, when the evidence suggested lime juice didn't work they w…
Exactly
'Chesterton's fence' is the principle that reforms should not be made until the reasoning behind the existing state of affairs is understood.
Re: Scott and Scurvy (2010)
#7Earlier quoted context omitted.
I suspect scurvy in particular is an unusually poor model of Chesterton's fence. There were centuries of incredibly stupid ideas before the use of lemons came along, and the benefits of lemons were not obvious, or other nations would have adopted the practice. Blindly keeping with tradition would have helped only in the switch from lemon juice to lime- indeed, when the evidence suggested lime juice didn't work they w…
they didn't have any real idea of the underlying mechanism Exactly 'Chesterton's fence' is the principle that reforms should not be made until the reasoning behind the existing state of affairs is understood.
As an aside, this also highlights one of the key flaws with Chesterton's fence, or at least its overuse: there is almost always _something_ that we don't understand about our changes. In the case of the limes, they understood that citrus fruit helped, but they didn't have the correct biological mechanisms by which it functioned. But this is true today - there are plenty of subjects where we understand lots of things about how something functions, but don't necessarily understand why it behaves that way. And that's just the cases where we know we don't understand something. There are surely many completely unexpected scientific discoveries to come. If we were to apply Chesterton's fence too liberally, we'd get very little done.
The same applies to more mundane cases. In terms of code, I'm generally a big fan of understanding why some feature was implemented before I start making changes to it, but I've had cases where I've tried to understand the original reasoning, but that reasoning later turned out to be wrong. Sometimes the best thing to do is simply to throw out all the old and embrace the unknown, accepting that it will probably go wrong in some ways, but also hoping that a new approach can be found.
So while I'm generally a fan of Chesterton's fence, I think it's important to recognise that it's just one approach in a toolbox of many valid but often contradictory approaches.