Demoralized developer’s desperate hack came back to haunt him on LinkedIn

← Back to the feed

Demoralized developer’s desperate hack came back to haunt him on LinkedIn

The Register · 3 hours ago

A developer, referred to as "Walter" for anonymity, shared a story with The Register's "Who, Me?" column about a hasty workaround he implemented while upgrading systems from Python 2 to Python 3 at a company beset by repeated layoffs and low morale. Rather than properly fixing the roughly 20 percent of systems that refused to cooperate with the upgrade, he created a symbolic link making Python 3 point to Python 2, expecting it to fail spectacularly but instead finding it worked without complaint. The tale illustrates how workplace stress and understaffing can lead to quick fixes that persist far longer than intended, quietly underpinning critical infrastructure.

Walter left a self-deprecating comment in the configuration script acknowledging the hack, then moved to a new job. Eight years later, he spotted a LinkedIn post from a former colleague announcing that the Linux upgrade project had finally been completed, and that his old symbolic link had been discovered after surviving a migration from a script to Ansible. The story is one of several anecdotes The Register's readers have submitted about workplace mistakes and improvised solutions coming back to light years later.

  • Developer symlinked Python 3 to Python 2 as a shortcut fix
  • The workaround worked silently for years, undetected
  • He learned its fate eight years later, via LinkedIn

Business Companies Cybersecurity Software Technology

Read the full article at the source →