So today I discovered that there's a cron job that holds non-reproducible state that died, and now our system is fucked.
The cron job doesn't live inside any source control. This morning it entered a terminal state, and because it overwrites its state there's no way to revert it.
I'm currently waiting for the database rollback and have rewritten it in a reproducible/idempotent way.
What's extra frustrating is the previous guy did create a git repo of these types of hacks, but this one doesn't live in it for no discernible reason.
Job security
But the whole point of the doomsday machine is lost... if you keep it a secret! Why didn't you tell the world, eh?
It was going to be announced at his retirement party on Monday... You know the dev likes surprises.