Code golf is the practice of solving a programming task in as few bytes or characters as possible. The goal is compactness, not readability or maintainability, so golfed code often uses dense syntax, shortcuts, and language quirks to shrink size. In security work, this matters because extreme compression can expose how an interpreter, parser, or sandbox really behaves when assumptions and safeguards are stripped away.
Attackers sometimes use code-golfed payloads to fit within tight input limits, bypass simple filters, or conceal intent in very small scripts. Defenders use the same mindset in reverse: they create minimal proof-of-concept programs to test whether a validator, scanner, or execution environment handles edge cases safely. Code golf is useful for demonstrations, but it can also hide dangerous ambiguity. A tiny program may look harmless while still triggering unexpected behavior in a runtime or control flow that was never hardened for it.