Ciamos

Mathematicians hunt elephants by going to Africa, throwing out everything that is not an elephant, and catching one of whatever is left.

Experienced Mathematicians attempt to prove the existence of at least one unique elephant before proceeding to step 1 as a subordinate exercise.

Professors of Mathematics prove the existence of at least one unique elephant and then leave the detection and capture of an actual elephant as an exercise for their graduate students.

Computer Scientists hunt elephants by exercising Algorithm A:

1. 1. Go to Africa.
2. 2. Start at the Cape of Good Hope.
3. 3. Work northward in an orderly manner, traversing the continent alternately east and west.
4. 4. During each traverse pass,

• (a) Catch each animal seen.

• (b) Compare each animal caught to a known elephant.

• (c) Stop when a match is detected.

Experienced Computer Programmers modify Algorithm A by placing a known elephant in Cairo to ensure that the algorithm will terminate.

Assembly Language Programmers prefer to execute Algorithm A on their hands and knees.

Database Adminstrators do not need to go out and capture elephants when they can retrieve them simply with an ad hoc query:
SELECT * FROM AFRICAN_CRITTERS 2 WHERE CRITTER_TYPE = ‘TERRESTRIAL’ 3 AND SIZE = ‘LARGE’ 4 AND COLOR = ‘GRAY’ 5 AND TRUNK = ‘YES’ 6 AND ODOR IS NOT NULL;

Engineers hunt elephants by going to Africa, catching grey animals at random, and stopping when any one of them weighs within plus or minus 15 percent of any previously observed elephant.

Systems Integration Engineers are not so concerned with hunting elephants as with creating a seamless interface between the elephants and their environment.

Economists don’t hunt elephants, but they believe that if elephants are paid enough, they will hunt themselves.

Statisticians hunt the first animal they see N times and call it an elephant.

Consultants don’t hunt elephants, and many have never hunted anything at all, but they can be hired by the hour to advise those people who do.

Operations Research Consultants can also measure the correlation of hat size and bullet colour to the efficiency of elephant-hunting strategies, if someone else will only identify the elephants.

Politicians don’t hunt elephants, but they will share the elephants you catch with the people who voted for them.

Lawyers don’t hunt elephants, but they do follow the herds around arguing about who owns the droppings.

Software Lawyers claim that they own an entire herd based on the look and feel of one dropping.

Vice-Presidents of Engineering, Research & Development try hard to hunt elephants, but their staffs are designed to prevent it. When the vice-president does get to hunt elephants, the staff will try to ensure that all possible elephants are completely pre-hunted before the vice-president sees them. If the vice president does see a non-pre-hunted elephant, (in other words, a live one) the staff will:

1. 1. Compliment the vice-president’s keen eyesight, and
2. 2. Enlarge itself to prevent any recurrence.

Senior Managers set broad elephant-hunting policy based on the assumption that elephants are just like field mice, but with deeper voices.

Quality Assurance Inspectors ignore the elephants and look for mistakes the other hunters made when they were packing the jeep.

Sales People don’t hunt elephants, but spend their time selling elephants they haven’t caught, for delivery two days before the season opens.

Software Sales People ship the first thing they catch and write up an invoice for an elephant.

Hardware Sales People catch rabbits, paint them grey, and sell them as desktop elephants.

Source unknown but tracked back as far as Chaos Corner in 1992 where it is attributed to 'Peter Theobald, National Center for Software Technology, Bombay, India.'