Notice Concerning Local Works Defense
An engineer trusted a change because it worked locally, which is the precise condition that makes the problem invisible.
Forensic Analysis: Local Works Defense
Subject: A configuration change deployed to staging that behaved differently than it did locally.
Evidence, Phase 1: Local Confidence
The change was developed over two days. During development, the engineer ran it locally approximately thirty times. It worked each time. Confidence was high.
The local environment used a seeded database. A mock external service. A configuration file that had been manually adjusted eighteen months ago by a previous engineer and never reviewed since. The local environment was stable. The local environment was wrong.
The engineer knew the environments differed. This is standard knowledge. The engineer did not investigate which specific differences were relevant to this change. This is also standard.
The governing rule applies: a technical shortcut may remain temporary for as long as nobody writes down its expiration condition. The "it works locally" confidence was temporary. Nobody documented its expiration condition.
Evidence, Phase 2: Staging
The change was deployed to staging at 2:14pm on a Tuesday. The staging environment uses a real external service connection. An environment variable set differently than local. An authentication timeout of fifteen seconds rather than the local mock's infinite tolerance.
The change failed at 2:17pm.
Evidence, Phase 3: The Defense
The engineer confirmed the change worked locally. This is accurate. The engineer proposed that the failure was a staging environment issue. This is also possibly accurate.
Investigation into which claim was correct would have taken thirty minutes. The investigation was not performed.
The change was redeployed with a minor modification. It worked. Nobody confirmed why the original failed or why the modification fixed it.
Finding: The local environment is evidence of nothing except the local environment. It is used as evidence of everything. The behavior persists because it is faster than investigation, which is exactly when investigation matters most.
Status: The change is live in production.