I wasn't the instigator but my reputation made me the prime suspect
This joke goes back to the early 1980s, and it wasn't I who was the instigator, but it turns out that I had done enough things like it that I was blamed for it. And I took that as the highest compliment.
I worked in a microcircuits design group. One co-worker we'll call Bob was a pretty theoretical guy--Ph.D, analyzed problems to a fault, took much longer to get to the bottom line than a practical person would by simply by taking the Thomas Edison approach.
The instigator--we'll call him Fred--was a very practical, hands-on guy, who would just go in and chug through a problem to get it done, then do the fine tuning later. Needless to say, there was friction.
We worked in a high noise environment. Our second-level manager happened to have a white noise generator at his desk to cover ambient noise and reduce stress, and Bob asked to borrow it one day to see if he wanted to get his own.
Manager said he would drop it at his desk at the end of the day, and Bob should try it all day tomorrow, as that's the only way to really give it a good assessment.
The manager dropped off unit, and Bob left for the evening. Fred sprang into action. He disassembled the white noise unit, happily noted that the 120 V power into the box was switched through a DPDT switch, and found a battery and a lift truck backup alarm in the engineering stockroom--which he proceeded to wire across the unused half of the DPDT on/off switch.
It all squeezed inside the box, so he taped it down tight, reassembled the unit, and replaced it at Bob's desk.
Next morning, Bob came in, plugged it in, hit the switch, and of course the backup alarm blasted away and drowned out the white noise, which was still working.
Bob jumped up, amazed.
Quickly his curiosity led him to come up all sorts of theories about what happened--seed for shift register got the bits synchronized in a long 1111...0000 combination, one in a million chance that this could happen, etc. blah blah blah.
He went to manager to express amazement and explain all of this. Somewhere in the process, though, the unit got unplugged and used as exhibit "A" to explain his long-winded theories about what happened, without Bob noticing that the power cord was dangling down on the floor by his feet while the alarm was still blasting away--at least until manager noticed, grabbed the plug end of the cord, and held it directly in front of Bob's face.
After staring at it a few seconds, the idea that it was a joke finally sunk in. They took it apart, discovered the modification, and went looking for the instigator--which they thought was me.
My protestations of innocence only reinforced in their minds that I had done it.
Fred only admitted to me much, much later that it had been him.
Guilty as charged...kind of.... I've fallen into this trap a couple of times.... assuming that the same symptoms are the same problem as last time. However I do keep an open mind and usually get onto the right track fairly quickly. Rule No. 1....NEVER assume......
Have any of you suffered from the theorist who learns that a certain problem causes a certain symptom and is then incapable of understanding that the appearance of that symptom does not necessarily indicate an occurrence of the same problem? I don't have an illustration to hand but trying to explain the fallacy can drive you close to madness.
Some of my coworkers will recognize these. A cursor controlled from remote location while the user's mouse still has some control over the cursor. This was good for a couple of laughs. The other one was to magnetize the users CRT while the user was not around. The user ran a lava lamp type screen saver and tried to come up with explanation for why CRT would become magnetized. The user would degauss the CRT to fix problem but the next day the problem would reoccur because one of his coworkers would re-magnetize the CRT before he got to work. One day the user was shown the magnet that was used to make the mysterious event occur thereby ending any of the possible complicated reasons for the problem. This is a lot like magic that uses a shill, it works very well. We often make assumptions based on what we think is normal. These are both cases where Occam's razor works well to try and understand the problem.
Great story John...I wonder whether there are any collection of engineering stories published somewhere...perhaps having a book that covers them would make engineering more interesting to a public at large...Kris
At some point in the life of a technology startup company, the CEO and the founding team will be confronted with the question of whether to sell the company or not. Hopefully, the question arises in a positive context and comes from an interested buyer driven by the opportunity to deploy the new technology to a much larger user base.
The IoT, wearables, and 3D printing-focused Designers of Things conference has also partners with the IPSO Alliance to call on entrepreneurs, makers, students, and professional engineers to submit designs using IP.