TECH Signal 426
Developer called five years after quitting to fix sabotaged Pick system that was simply unplugged
↗
A developer was summoned by his former boss five years after leaving because a fired clerk had unplugged the Pick minicomputer running a mail order business, and the recovery only required plugging it back in and rebooting.
The story illustrates how legacy systems can create single points of failure when operational knowledge concentrates in one person who leaves. The sabotage was trivial, unplugging a machine, yet caused a business crisis because no remaining staff could diagnose it, and the original developer could charge a premium for emergency support of a system only he understood.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
A fired clerk unplugged a Pick minicomputer while it was printing orders, which the business treated as a critical failure.
The former developer who wrote the system's software was called five years after quitting to resolve the issue.
The fix involved plugging the machine back in, booting it up, checking data, and restarting the print run, for which the developer charged a lucrative fee.
THE CLUSTER