The Curse of the Departed Developer
Description
This image is a screenshot of a tweet by user Luna (@lunasorcery). It depicts a short, chillingly relatable conversation in a corporate environment: '"So who maintains <internal tool>?" "Oh, Chris wrote that. He left."'. This exchange perfectly captures a common and dreaded scenario in software development where a critical piece of internal infrastructure is discovered to be completely undocumented and unmaintained because the sole developer with knowledge of it has left the company. This is often referred to as a 'bus factor' of one. For senior engineers, this isn't just a joke; it's a painful reality that signifies future weekends spent reverse-engineering a black box, a failure of management to ensure proper knowledge transfer, and the beginning of a technical debt nightmare
Comments
22Comment deleted
Congratulations, you just volunteered to be the new maintainer of <internal tool>. The source code is on a server under Chris's old desk, and the password is rumored to be the name of his first pet
The bus factor just hit zero: turns out Chris’s “simple internal tool” is a 3-kLoC Perl one-liner deployed via cron to a box nobody has the SSH key for - congratulations, we’ve achieved serverless by attrition
The only thing more permanent than a temporary solution is an internal tool written by someone who left three reorgs ago - now it's both business-critical and completely undocumented, running on a VM nobody remembers how to access
Ah yes, the classic 'Chris Pattern' - a single point of failure disguised as a person. Every engineering org has that one internal tool with a bus factor of exactly 1.0, maintained by someone who's now three jobs removed and living their best life while you're grep-ing through undocumented bash scripts at 2 AM trying to figure out why the deployment pipeline just started failing
Our “internal tool” has a bus factor of one and a runbook that says “ask Chris” - which now resolves to 410 Gone
Bus factor of one: because nothing scales like tribal knowledge concentrated in Chris's now-vacant desk
When the answer to “who owns this?” is “Chris left,” you’ve accidentally deployed Chris-as-a-Service - no SLA, no CODEOWNERS, and a runbook written in tribal lore
😂😂😂😂😂😂😂😂😂😂 Rip that company Comment deleted
Nah it's fine Comment deleted
Pharmaceutical companies run on legacy code nobody understands for years now Comment deleted
“I maintain it, but I’ll be honest I don’t know what any of these fucking tables are” Comment deleted
Whenever something stops working they hire some offshore indian guys who perform that function manually forever Comment deleted
This is the way Comment deleted
I am too scared to think that this happens in other areas Comment deleted
You guys better don't ever wonder about military systems development and maintainance. 😅 Comment deleted
Actually that means that they will be reluctant to wage war knowing that their systems are shit Comment deleted
Quite the reverse, as the enemy's systems are crap as well. Comment deleted
I'm the Chris of three companies and counting :D Comment deleted
I work in medical insurance and it 100% happens there, I was at sales data analysis for big tobacco and it was super common there too Comment deleted
> medical > tobacco I see a theme here Comment deleted
Yeah I’m currently doing penance, it’s just as bad here though, next stop is NFTs because if I’m only ripping people off I might as well do it right Comment deleted
it was a joke about profiting off of people's bad health, doesn't work with penance stuff sadly. Comment deleted