An anti-pattern is not forbidden syntax. It is a recurring shape that solves the immediate problem by creating a larger one.
These pages deliberately include historical DreamWeave code. The point is not to dunk on old code. The point is to show why the modern rule exists.
If an anti-pattern has a sufficiently expensive historical failure attached, it also appears under Paid For With Blood.
Protected Execution Everywhere
Catching failures you cannot recover from only delays the useful crash.
Every Frame Is a Budget, Not an Invitation
Poll only what must be fresh, batch what can be late, and move observations to their natural owner.
Probing Context by Failure
A historical compatibility trick that should not become ordinary module architecture.
Clever Proxies and Magic Tables
Metatables can unify APIs; they can also hide every important ownership decision.
Cargo-Cult Optimization
A fast-looking source transformation is not evidence that the workload got faster.