Higgs Bugson
Updated 2026-08-08
INTRODUCTION
English translation pending.
CORE DEFINITION
Named by analogy with the Higgs boson, which can only be detected indirectly, a Higgs bug is a defect whose existence is inferred from event logs or downstream failures but which cannot be reproduced in a development environment. The core claim is that the observer changes the system: adding logging, attaching a debugger, or slowing execution alters timing and memory, so the conditions that produced the failure no longer hold. Key qualifications are that such bugs usually live in concurrency, timing, or state-dependent code, and that they must be attacked by reasoning and defensive design rather than by reproduction.
SCAFFOLDING EFFECT
Reduce cognitive load
- Reason from logs: reconstruct the causal chain from recorded events rather than from a live repro. - Defend broadly: harden the whole subsystem instead of patching the one suspected line. - Keep observation light: use sampling and metrics that do not alter timing or memory.
Anchor fast decisions
Concurrency and timing defects depend on an exact interleaving of events that occurs only under production load. Any observation mechanism, whether a print statement, a breakpoint, or an attached profiler, adds delay or memory that changes the interleaving, so the defect disappears precisely when you look for it. The evidence therefore stays indirect, and the practical response is to reason from logs and to design the subsystem so that the failure mode cannot occur.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Heisenbugverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS