On Tue, Mar 13, 2012 at 3:24 AM, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote: > On 12 Mar 2012 00:30:08 GMT, Steven D'Aprano > <steve+comp.lang.pyt...@pearwood.info> declaimed the following in > gmane.comp.python.general: >> I expect that naming rule was invented by either people who have heard of >> test driven development, but never actually done it, or by people so >> anally-retentive that if they make seven short car trips over an hour, >> they check the tyre pressure, oil and water seven times because "the >> manual says to check before *every* trip". >> > By which time they find they have to add air, oil, and water as: the > pressure gauge usage lets out some air each time; they've wiped a few > drops of oil onto a rag each time; and the radiator was still > hot&pressurized such that they got an "overfull" result.
In defense of such rules: There's a period in every new programmer's life when it helps to learn a whole lot of principles; and if he's working on some collaborative project, rules are the easiest way to demand such behavior. Later on, you learn how and when it's safe to break the rules (and/or how to deal with rule conflicts), but the rules still have value. Just never treat them as laws of physics (in Soviet Physics, rules break you!). ChrisA -- http://mail.python.org/mailman/listinfo/python-list
