When your 'temporary' comment gets immortalized in the git diff forever
Description
The image is a two-part Twitter screenshot using the dark TweetDeck theme. In the first tweet, the user writes “uh huh.” above a clipped IDE view showing green comment text “//temporary” followed by the keyword “try” in pastel pink on a black background - clearly a quick hack left in the code. The follow-up tweet says “I don’t want y’all to worry, I fixed it.” and shows a classic git diff: a red deletion line “//temporary” and a green addition line “// Permanent”, both above the unchanged pink “try”. The joke plays on how throw-away comments and hacks survive code reviews and become permanent, highlighting technical-debt, code-quality problems, and the realities exposed in version-control diffs
Comments
8Comment deleted
The only thing with stronger durability guarantees than our S3 Glacier tier is the ‘//temporary’ workaround that got promoted to //Permanent in today’s diff
The only thing more permanent than a temporary fix is the git blame that will haunt you when it inevitably becomes load-bearing infrastructure three acquisitions later
Ah yes, the classic 'ship it and forget it' pattern - where 'temporary' is just a comment away from becoming a load-bearing architectural decision that survives three rewrites, two acquisitions, and outlives the original author's tenure. Nothing says 'enterprise-grade' quite like a try-catch block that's been in production longer than some of your junior devs have been coding. At least he documented the transition from technical debt to technical mortgage
We finally made it official: the “temporary” try is now a Permanent fixture - because in production, hotfixes have a higher SLA than refactors
Nothing nukes tech debt like a green diff turning //temporary into //Permanent - congrats, it’s now an ADR
'// temporary' fixes: outliving Moore's Law since the first hack
lgtm Comment deleted
// Permorary Comment deleted