Software
A script that shouldn't have worked, on a project that never ended, for a company that hardly cared
WHO, ME? The past may be a foreign country, but it's one The Register likes to explore each Friday in "Who, Me?" – our reader-contributed column that shares your tales of workplace mistakes and great escapes.This week, meet a reader we'll Regomize as "Walter," who once worked for one half of a duopoly competing in the intertwined markets for bad poetry celebrating memorable life moments and questionable television dramatizing the sentiments in those poems.The duopoly didn't make for a stable industry. "We produced a steady cycle of layoffs and hiring," Walter lamented.
He nonetheless survived the latest round of layoffs and found himself upgrading systems from Python 2 to Python 3. "Our vendors had stopped pretending Python 2 was still a reasonable life choice," he told The Register.
That move coincided with an upgrade to a new version of Linux that happily ran Python 3."The older one technically could too, but only after a series of rituals involving symbolic links, configuration tweaks, and what I can only describe as informed superstition. It worked on about 80 percent of our systems and the remaining 20 percent flatly refused to cooperate for reasons nobody could explain."Walter told us he blamed the problem on a recent change of vendor in the office cafeteria. "It fit the evidence about as well as anything else," he wrote.Everyone on the team knew the upgrade-resistant 20 percent had to be fixed, but the recent redundancies had left morale so low that nobody was willing to pull the necessary all-nighters.The fact that some of the staff had decided to drink their way through the situation didn't help either."One morning, fueled by spectacularly bad coffee and the news that a job interview had been pushed back another week, I had what can only be described as a terrible idea," Walter admitted. "What if I simply pointed Python 3 at Python 2?"
