Attention people who think UB is fine

Undefined behavior in C is far more dangerous than commonly assumed—it doesn't just cause predictable segfaults or execute code as written. The author demonstrates through compiler examples that UB can cause completely unrelated functions to execute (like `explode()` being called without being invoked), write unexpected values to memory, or crash via invalid instructions, depending on how the compiler optimizes the code. Compilers are not obligated to detect or consistently handle UB, making it impossible to predict what will actually happen at runtime.