[117398] in Cypherpunks
Re: why bad things happen to good systems (fwd)
daemon@ATHENA.MIT.EDU (Jim Choate)
Thu Sep 2 13:46:55 1999
From: Jim Choate <ravage@einstein.ssz.com>
Message-Id: <199909021726.MAA08692@einstein.ssz.com>
To: cypherpunks@einstein.ssz.com
Date: Thu, 2 Sep 1999 12:26:25 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: Jim Choate <ravage@einstein.ssz.com>
----- Forwarded message from Anonymous -----
Date: Thu, 2 Sep 1999 18:00:47 +0200 (CEST)
From: Anonymous <nobody@replay.com>
Subject: CDR: Re: why bad things happen to good systems
bad things happen to good systems because human beings aren't as perfect
as they think they are.
Had one like that at CESR once too : outside group's experimental setup
involving a tank of H2., main valve failed, 2nd valve failed, regulator
failed, tubing split, big leak...fortunately no source of ignition
...you'd think they would do a dry run of their equipment outdoors.
----- End of forwarded message from Anonymous -----
Bad things happen to good systems because even good systems can fail,
they're not perfect either.
I speak from experience, I'm blind in one eye, both ankles and knees are bad,
slightly crippled right hand, had just about every joint in my body
dislocated at one point or another, several muscles damaged from severe
tears and resultant scar tissue, luckily no broken bones. And I still do
stuff that most folks think is just plain crazy. I think they're just plain.
____________________________________________________________________
Man is the best computer we can put aboard a spacecraft - and
the only one that can be mass produced with unskilled labor.
Werner von Braun
The Armadillo Group ,::////;::-. James Choate
Austin, Tx /:'///// ``::>/|/ ravage@ssz.com
www.ssz.com .', |||| `/( e\ 512-451-7087
-====~~mm-'`-```-mm --'-
--------------------------------------------------------------------
