|
|
|
good chemistry is complicated, and a little bit messy -LW |
|
| PerlMonks |
About white shoesby tilly (Archbishop) |
| on Dec 02, 2000 at 03:09 UTC ( [id://44552]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
After talking with neshura, she didn't know the answer
to the question about why white shoes were banned after
Labour day, and why the rule disappeared. She just wanted
people to think about rules that continue existing long
after the reason had been lost. Well I don't definitively know the answer, but I have a theory. After wandering around for a while (hitting some odd places) I found enough mentions that the original rule was not just white shoes, but white (or light colored) clothing in summer to keep the heat off. Therefore your shoes were white to match your summer clothes. And the reason for saying that you only wore them from Victoria Day to Labour Day was that that was a traditional definition of summer. So wearing white shoes outside of that period was admitting that you either couldn't recognize summer clothes, or you didn't know what time of year it was! Well then why was the rule lost? I don't think that there was any particular reason. Rather, over the last century, the rules on garb have been relaxing. All sorts of little rules have been lost, and this is but one of the casualities. I believe that the first was the spread of women wearing male pants from riding to general wear. This was a sight that originally was regarded much as we might regard men today wearing dresses. But it isn't just women's clothing that has changed. For instance shirts used to be underwear. Then it became acceptable to take your jacket off. Then the undershirt evolved into today's t-shirt. Anyone who wants some interesting tidbits and quotes about fashion should take a peek here. But enough about shoes. Here are some more rules to show how things survive long after everyone has forgotten the point:
The same is true in any human endeavour. Not just in the social rules, but in various other good rules we learn. For instance in programming you will find many rules about things like eliminating needless redundancy, modularity, avoiding goto, so on and so forth. These are generally good rules. But each one is a good rule for a reason, and there are limitations to the rule. For instance if you can find it, Structured Programming with goto Statements by Donald Knuth (Computing Surveys, December 1974) may cause you to question the received wisdom that goto is always harmful. Likewise reduced typing is good because maintaining multiple documents is a good way to cause bugs. However Exporter recommends putting things that you want to export into @EXPORT_OK rather than @EXPORT. This is true even though it forces you to type more! Why would they force this? Well because the rule about typing is far less important than the observation that you should strive to put things that logically belong together, together. Most modules should not be by default setting policy for packages that use them, and if in a file you see a function, you shouldn't have to go looking all over to figure out where that function was defined! And this is what had been the main thing that I disliked about princepawn's posts. He would consistently take a good rule - such as eliminating redundant typing - and apply it to places where it clearly didn't really fit. Just because a rule is claimed to be good, and good programmers agree that it is, doesn't mean that it is always applicable. But to get a sense for when it is and is not, you need to understand why the rule exists. Else you may find yourself doing something that really makes no sense. (Like trying to volunteer information to a police officer who will then turn the transcript over to a lawyer who in a literal sense will attempt to destroy you in ritual verbal combat. Oops.)
In Section
Perl Monks Discussion
|
|
||||||||||||||||||||||||