Cardboard Analyst  Faced with a scarcity of people available to
grab for DebugByDescribing sessions, one engineering
organization acquired a CardboardAnalyst from a local video
store.  Why is that developer trying to explain two-phase commit
to a big cardboard wookie?  Don't ask. It is not unusual to be
helping someone by listening to their tale of woe when all of a
sudden they proclaim AHA I know what it is and suddenly you have
been turned into a CardboardAnalyst.  And nice people say "Thank
you" before hacking away on their keyboards. :)  Or after
hacking away on their keyboards. It wouldn't do for them to
forget whatever they just realized by doing something else
before using it, such as calling a thank-you routine that
potentially overwrites the register it's sitting in! Lack of
register-saving around nested calls seems to be a design flaw in
whatever it is that we were compiled with.  I wonder why we have
to talk to activate our thinking. Just thinking in my mind is
not effective as talking though the s