Just because it fails doesn't mean it's a failure
Flashback to the early 1980s, when this pilot has just joined the engineering support team at a big computer vendor.
"A customer had a Cobol program that was intermittently failing," says fish. "Field support found it was only failing when it ran on one of the customer's two processors.
"They ran the diagnostic checks, but didn't find any issues with the processor it was failing on. In those days, each processor was five feet by five feet with a couple hundred printed circuit cards and miles of copper wire on the backplanes.
"So our group was called in -- a software guy and a hardware guy. They got to the site and confirmed hardware was the culprit. The hardware tech went into the cold room. Four hours later, he came out, announcing it was fixed.
To read this article in full or to leave a comment, please click here