"J. van Baardwijk" wrote:
>
> At 23:42 19-2-02 -0600, Ronn Blankenship wrote:
>
> >>Generally we ascertain what they want, and then build it correctly based on
> >>experience as to what will blow up or catch on fire or not work.
> >
> >
> >
> >Of course, that experience is usually gained by building numerous things
> >that either blew up, caught on fire, or at least smoke-tested a
> >several-hundred-dollar piece of test equipment . . .
>
> But then, that usually *is* the best way to learn how to do something: by
> first screwing up big time. Quite frankly, I am amazed I have never fried
> any computer components. Yet.
>
> Hm. Better keep me away from the controls of a nuclear power plant... :-)
>
> Jeroen "what does this button do?" van Baardwijk
Heh. At my last job, we had software that employees had written for
internal use. If I was going to be using the software directly, they'd
give me access to it for testing. If there was some way to crash it,
I'd find it pretty promptly, and not intentionally. :) They wouldn't
let me touch the more delicate systems that were held together with
figurative bailing wire....
Julia "will crash software for food" Thompson
