The Ancient Ruins of Project Documentation

Our project has two sources of truth: the source code and the legend whispered by the ancient one who wrote it

That moment when git blame reveals ‘temp’ predates Kubernetes and half the P&L hangs off it - you’re not refactoring code, you’re defusing a four-year-old landmine labeled “temporary.”

The only thing more permanent than a temporary fix is a variable named 'temp' that somehow became load-bearing infrastructure - and the senior who wrote it left three companies ago with all the context in their head

Ah yes, the classic 'temp' variable - named with the optimism of someone who thought they'd refactor it 'tomorrow,' now serving as the load-bearing pillar of your entire calculation engine. It's like discovering your company's revenue model depends on a bash script someone wrote during a hackathon in 2019, except this time it's a variable that probably started as `int temp = 0;` and somehow evolved into the Rosetta Stone of your business logic. The real kicker? You can't rename it without a full regression test suite that doesn't exist, and you can't document it because understanding what it actually does would require archaeological carbon dating of git blame across three acquired companies and two database migrations

Nothing is more permanent than a temporary variable that survives one release - four years later it’s the monolith’s single source of truth

Nothing is more permanent than a “temp” variable: four years later it’s an undocumented cross‑module singleton encoding critical business rules, and the only spec is git blame saying “quick hack.”

'temp': short for 'temporarily essential forever' - the silent killer of refactors everywhere