Lessons on Rules from the Pinewood Derby Post: 302261754

Sponsored Content

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Lessons on Rules from the Pinewood Derby Post 302261754 by Linux Bot on Tuesday 25th of November 2008 01:08:53 PM

11-25-2008

Registered User

Lessons on Rules from the Pinewood Derby

Tim Bass
11-15-2008 09:11 AM
Remember all the fun we had when we carved out race cars for our Pinewood Derby? For those of you are were not apart of this great American Cub Scout culture, the pinewood derby is a racing event for Cub Scouts in the Boy Scouts of America. Cub Scouts, with the help of their parents, friends and kits, carve and build their own cars from wood. Cub Scouts usually start from pinewood derby kits containing a block of pine, plastic wheels and metal axles. These events are so popular, the pinewood derby was selected as part of “America’s 100 Best” in 2006 as “a celebrated rite of spring” by Reader’s Digest magazine.

Well, it so happens I was doing some research into rule complexity and what defines “complex” and “complexity” in rule-based systems, when I ran across an article on rules and the pinewood derby. Here is a few quotes from Rule complexity (Rules, Part 2), which I thought you might enjoy.

When creating complicated rule sets, people tend to create many rules are subjective or are difficult to enforce. How do the race inspectors examining wheels ensure that they weren't lathed? Are they weighing each wheel? Visually, lathed wheels can appear to be completely stock. Some races have prohibitions on cars from previous years or on pre-cut cars. The intent is to keep kids from using last year's car. I agree with the intentions - building the car is part of the fun. But who can tell for certain which cars are pre-cut or a re-paint of their older brother's car? Rules like this should be presented as guidelines that should be followed instead of rules that should be enforced.

We see so many software vendors running to sell us their lastest rule-based framework, and the network and blogosphere is buzzing with rule discussions.* So, keep this in mind, as our friend from the pinewood derby lamented:

The problem with trying to create a rule to cover every possible situation is that you can't possibly think of every possible situation.* [...] - understand[s] that the rules can't cover everything. The more complicated you make your rules, the more impossible they will be to enforce. You'll introduce conflicts, ambiguities, and loopholes - [...].

I realize a few of my colleagues (most one that are are selling rule-based systems) wish I would stop blogging and just dissappear into cyberspace without a trace left behind.* They think I have lost my marbles because I cannot jump on the “hype up rules bandwagon!” ** To simply disappear into the ether would be the easy road to go, because for anyone who actually has worked in complex operational problems (not just selling software or “talking the talk”), they understand very quickly that, as our friend at the pineword derby so nicely put it, you can't possibly think of every possible situation, rules cannot cover everything.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

4 More Discussions You Might Find Interesting

1. Solaris

Private Lessons

Hi everyone, I'm looking to hire for private lessons a individual who is presently working as a unix system administrator or instructor in school who is teaching unix. I live in Clifton nj my nubmer is Cell **no phonenumbers on this forum** or email **no emails on this forum** please let me...

2. Programming

C Lessons

I started wrting c lessons for absoulute begginers to advanced users, I think material can be considered quality, and my students learn programming with this stuff. If you wish feel free to start reading it here: www.visualcmaniac.com its only 5 lessons for now so maybe could be easier for...

3. What is on Your Mind?

The 5 Minute Management Course (Six Lessons)

Lesson 1: A man is getting into the shower just as his wife is finishing up her shower, when the doorbell rings. The wife quickly wraps herself in a towel and runs downstairs. When she opens the door, there stands Bob, the next-door neighbour. Before she says a word, Bob says, 'I'll...

4. What is on Your Mind?

vi/vim lessons 1 - 7

Basic Editing https://www.unix.com/members/neo-albums-forum-pics-picture525-vi-vim-tutorial-1-basic-editing.gif

LEARN ABOUT DEBIAN

accc

Ac3d Compiler(6)						       Games							  Ac3d Compiler(6)

NAME

       accc - Ac3d Compiler

SYNTAX

       accc [option] <inputfile> <outputfile> [dist][-order orderstring]

DESCRIPTION

       This manual describes the Ac3d compiler application that is shipped with the game TORCS.

OPTIONS

       -strip stripify any ac3d output models

       +o     ac3d  to	ac3d:  the result file is optimized in using groups by zone of track track must be named TKMNxxx dist is used to determine
	      the distance of the objects

       +om    ac3d to ac3d: the result is a vertex merged unique obj for smooth car only

       -o     ac3d to obj +s ac3d to ac3d with strips (used for cars)

       +es <angle_of_smooth>
	      ac3d to ac3d with strips (used for cars) and extended ac3d file output (computed normals) angle is in  degrees:  example:  +es  80.0
	      clkdtm_o.ac clkdtm.ac the output file will also contains the secondary textcoord for the env sliding

       +et    ac3d to ac3d with triangles (used for cars) and extended ac3d file output (normals normals)

       +etn   ac3d to ac3d with triangles no split and extended ac3d file output (normals normals)

       +shad  ac3d to ac3d with triangles, create a new ac3d file used for track shading vertical mapping of a single texture

       <inputfile>

       <outputfile>

       -order orderstring
	      only  used  with +es , +s and +et orderstring is the order of the objects during the save for example: HB;OB;OBM is the names of the
	      objet separate by a semicolon for imported NFS cars the object name HB must be used instead of: HB

       -g <outputfile>
	      for grouping multilayer ac3d track

       -l0 <input filename>
	      the base geometry

       -l1 <input filename>
	      the base geometry map-tiled

       -l2 <input filename>
	      the base geometry skids/and grass details

       -l3 <input filename>
	      the base geometry shadows

       -d3 <val>
	      the max distance of groups in tkmn

       -d2 <val>
	      the distance of group 2 in tkmn

       -d1 <val>
	      the distance of group 1 in tkmn

       -S <val>
	      the distance of splitting for TERRAIN* objects

       -es    for extended ac3d file format for strips

       -nts   no texture split (for debug)

SEE ALSO

       torcs(6)

AUTHOR

       This manual page was writen by Rudy Godoy <rudy@stone-head.org>, for the Debian GNU/Linux system (but may be used by others).

Rudy Godoy								1.4							  Ac3d Compiler(6)