|
|
|
| Authored by: Mikkel on Wednesday, May 30 2012 @ 08:18 PM EDT |
<humor>
It depends on the type of elevator button. If it is the type that lights up to
acknowledge that your request has been received, and it does not not light up,
you do not know if the problem is the light or the button. I have had to push
the button twice to call the car on then once. Sometimes it even takes a turning
push to clean the contacts and make it work.
Then there are the elevators that can be overridden by a key, and using the key
clears all the calls, so you have to press the button again.
And we must not forget the elevators that have human operators instead of
electronics to control the car. They are not that common any more, but you do
run into them. Pressing the button rings a bell, and sometimes lights up a light
that shows what floor is calling for the elevator. Pressing the button more then
once may be required to wake up the operator.
</humor>
[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Wednesday, May 30 2012 @ 10:15 PM EDT |
And to continue in the vein of the other responder...
>Ever tried to make a program do something more than once, knowing that it
caused it to crash the first time?
Sure. Depending on the error/exception, it could be a hardware problem such as
flaky memory. Running it a second time could load the program in a different
area of memory and run without error. A slowly failing hard drive might also
encourage you to try to copy of the data multiple times (perhaps after turning
off the system to let it cool down) in the hope that subsequent reads would be
more successful. Sometimes the latter actually works.[ Reply to This | Parent | # ]
|
| |
| Authored by: Gringo_ on Wednesday, May 30 2012 @ 10:50 PM EDT |
Me. You made me laugh at my own folly. The buttons on the
elevator in my
building don't have lights to show when they
were pressed. The elevator always
delays a few seconds
before responding by shutting the door and starting
towards
the requested floor. I always keep pushing the button,
because I don't
know if that delay is because the button
makes bad contact, or if it is a
programmed delay. Would you
believe that because of my impatience, I have never
once
tried simply waiting after pressing the button a single time
to see if it
is indeed a programmed delay as opposed to a
faulty button? Yet I am more than
90% certain that is the
case. Instead, like a fool I keep on pressing that
button
until it finally responds, every single time. I can't
explain this
irrational behaviour, except to by making weak
excuses about being human. It is
humbling.
[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Thursday, May 31 2012 @ 11:05 AM EDT |
A Software Engineer, a Hardware Engineer and a Departmental Manager were on
their way to a meeting. They were driving down a steep mountain road when
suddenly the brakes on their car failed. The car careened almost out of control
down the road, bouncing off the crash barriers, until it miraculously ground to
a halt scraping along the mountainside. The car's occupants, shaken but unhurt,
now had a problem: they were stuck halfway down a mountain in a car with no
brakes. What were they to do?
"I know," said the Departmental Manager, "Let's have a
meeting, propose a Vision, formulate a Mission Statement, define some Goals, and
by a process of Continuous Improvement find a solution to the Critical Problems
and we can be on our way."
"No, no," said the Hardware Engineer, "That will take far
too long, and besides, that method has never worked before. I've got my Swiss
Army knife with me and in no time at all I can strip down the car's braking
system, isolate the fault, fix it, and we can be on our way."
"Well," said the Software Engineer, "Before we do anything,
I think we should push the car back up the road and see if it happens
again."[ Reply to This | Parent | # ]
|
|
|
|
|
