
A fired clerk sabotaged a Pick system by unplugging it. The original developer spent the night fixing it and charged a fee that made the lost sleep worthwhile.
Wade built the software for a mail-order business in the mid-1980s. He wrote it on the Pick operating system, a minicomputer OS with a built-in database. He moved on to other work. His old boss didn't call for years.
Then one evening in early 1990, the phone rang. The boss had fired the clerk who ran the system. The split was not amicable. The clerk got an hour to pack up. She used that hour to unplug the Pick machine while it printed the day's orders.
Wade showed up at the office. He plugged the machine back in. He spent the next couple of hours booting it, checking data integrity, and restarting the print run. The boss was relieved. The day's orders were saved.
"The loss of a night's sleep was recompensed by the fee I charged," Wade said. He declined to name the exact amount.
For a small mail-order business, a downed system can mean lost revenue and frustrated customers. The story is a reminder that the person who wrote the code may be the only one who can fix it when things go wrong. And that a disgruntled ex-employee can cause damage even after leaving.
Drafted by a large language model from the source reporting linked above, then screened by automated publishing checks. It is not read by a journalist before publication. Some articles cite our Alpha Score. Verify prices and figures against the original source. Educational coverage, not personalized advice.