Avoiding the Technical Debt Collector
Description
This meme uses the 'Death Knocks' painting format. In the foreground, the Grim Reaper, depicted as a skeleton in a black, hooded robe holding a scythe, represents 'TECHNICAL DEBT'. He is standing on a porch and ringing the doorbell of a white house. In the background, a man in a white shirt and dark pants, labeled 'Quitting every two years', is seen fleeing the scene with a panicked expression. A watermark for 'https://Clear.ML' is visible in the bottom-left corner. The meme humorously illustrates a cynical career strategy where a developer contributes to or ignores accumulating technical debt and then leaves the company before the long-term consequences manifest. For senior engineers, this is a relatable and often frustrating scenario, as they are frequently the ones left to deal with the 'debt' left behind by predecessors who prioritized short-term gains over sustainable, quality code
Comments
9Comment deleted
That's not technical debt; it's a 'long-term architectural bond' that fully vests with the next engineer who touches the code
Leadership calls 24-month attrition “fresh perspective”; we call it the Bus-Factor summoning ritual - tech debt hears the chant and shows up at the doorbell
The two-year mark: when you realize the "temporary workaround" from your onboarding is now load-bearing infrastructure and the senior who wrote it is already at their second company since
The modern software engineer's career strategy: accumulate technical debt faster than compound interest, then execute a strategic exit before the principal comes due. It's not abandoning ship - it's 'pursuing growth opportunities' before your architectural decisions achieve sentience and hunt you down. The two-year mark isn't arbitrary; it's precisely calibrated to be after vesting but before anyone realizes that 'temporary workaround' you shipped is now load-bearing infrastructure supporting half the company's revenue
Quitting every two years: the ultimate tech debt refactor - nuke the repo and git init a new career
You can load-balance your career by quitting every two years; technical debt still has server-side session affinity and keeps ringing your doorbell
Keep average tenure at two years and your ADRs become Slack lore - the bus factor hits one and technical debt doesn’t knock; it already has a badge and prod access
this is not a dev problem. If PM (customer) requests to implement features instead of dealing wit tech debt - its their decision and their headache in the future. Devs have no reason to quit because of tech debt, because they would have to deal with someone else's tech debt on the other project. At the same time - solving your own mistakes is very useful for your growth. PS: meme is good btw 😅 Comment deleted
Well said. Sir Comment deleted