I’ve got a good one. And I’ll name names. Well, the company name at least, because that’s all I can remember, and because they deserve to be named.
Long ago in the earliest days of real typesetting from Mac DTP, probably around 1985, I worked at Graphics Plus in Culver City CA, one of the first Mac DTP service bureaus around. I was a computer tech and programmer, and I hired as a tech, but once I got into the company, there was a turf war with the owner and the Chief Tech, and I got shuffled off to sales, dammit!
We had two of the brand new, extremely expensive Linotronic imagesetters (costing something like $150k each), the first ones on the market. And the chief tech was so paranoid of anyone else that had technical skills that he’d never let me go near them. What an asshole.
So anyway, one day Chief Tech is encountering massive output problems. Pages don’t print, output is screwed up with garbage all over them or misplaced graphics and text, it was infuriating. Chief Tech was absolutely baffled, and spent several days trying to figure it out, to no avail. I offered to help debug it, but was rebuffed. And things were coming to a crisis because just before the problems set in, we had contracted with a local golf tournament to typeset their daily results, the jobs would come in at 5PM and we guaranteed delivery by midnight (with stiff nonperformance penalties). The job was coming in only a few days, and we were not even able to get more than about 10% of our current work out the door.
So in the midst of this, I’m sitting in my office, reading MacWeek, and fuming that my sales commissions are screwed because we’re not doing any work and we’re losing customers, when I come across a news article buried in the back. It described this new thing someone had discovered on their Mac, a computer virus. Nobody had ever heard of this before, and the article said that service bureaus on the east coast had encountered this and it wreaked havoc until they figured out what it was, and it described the symptoms which were PRECISELY what we were having trouble with. I immediately took the article to the owner, who didn’t understand it and told me to show it to the Chief Tech. I showed it to him, and with a harumph, he said it couldn’t possibly be our problem, it was a hardware problem. Ah well, screw em. I went home.
The next morning I came into work, and to my horror, there was Chief Tech sitting on the floor, amidst the wreckage of two entirely dissasembled imagesetters!! This was something you NEVER do, we had full service contracts, but the tech decided he could solve the problem on his own. He had attempted to create one working linotronic out of the parts of two linos, he thought it was a hardware problem. And in the process, he completely fucked both machines, they could not be reassembled. He turned $300k of fancy hardware into rubble, and we had no working equipment at all. The owner was having a fit. Now the super-ultra-rush jobs were about to come in that very evening, and we were completely offline. He had to call his business rival and offer them triple-danger-money to do the work for him, then deliver it back to our shop, and we’d pretend WE did the work and hand it to the client. He ended up paying tens of thousands of dollars out of pocket to fulfil his contractual obligation.
So as the shit hits the fan, I am absolutely fed up. While the tech is in the office with the owner, I snuck over to the macs (which Chief Tech had forbidden me to ever touch) and checked them for signs of viruses. And there it is, the little file in the system folder called “scores” which is the sure sign of the infamous “scores virus,” the very first mac virus. So I wait until the tech is out of his meeting, and go in to see the owner. I told him what I’d found. I yelled and yelled at him, how could he have allowed this idiot tech to cause this disaster when I’d already given him the solution several days ago and was completely ignored? I demanded that Chief Tech be fired immediately and replaced by ME. And he agreed with me. But then he dropped the bomb on me, the one fact that made the whole disaster clear in one flash. He said, “I’d like to fire him, but I can’t, he’s my biggest investor’s son!” Grrr…
Well anyway, the business losses were massive. Linotronic was not happy to see their machines dissasembled by Chief Ignorant Tech and it cost a LOT of money to get them reassembled and working properly. The losses kept mounting, we lost customers, didn’t have enough money to pay for supplies, and after a few weeks, the losses were so massive that the company had to lay off almost everyone, including me. Oh, but Chief Tech got to keep his job, even though he caused it all.
So I’m claiming to be the first person to lose their job on account of a computer virus. Well, mostly because of Chief Tech. And you know, once I’d found the cure, the problem could have been solved in 30 seconds.