How Backtesting Works, And What It Can't Tell You
Backtesting replays a strategy against historical data. What the process does, why results look better than they were, and how to read a report honestly.
Hot Topic
Position sizing, exposure limits, order gates and kill switches, how risk is enforced by systems rather than intention.
1 piece published on this topic · Updated
Risk automation is the difference between having rules about risk and having risk limits that hold. A position-size rule that a trader can override in the moment is a preference. The same rule implemented as a gate every order passes through is a constraint, and only the second one survives a bad afternoon.
Implemented properly it sits between strategy and execution as a separate stage, not inside the strategy. That placement is the point: if sizing and exposure checks live in strategy code, a defect there can produce an order no limit would have permitted, and the limits were never really limits. As an independent gate, the checks hold regardless of what the strategy asked for.
It also concentrates the controls that matter in an emergency into one place. A kill switch in the gate stops new entries across every strategy by flipping one flag, without a deploy and without editing strategy logic. The value of that is measured entirely in situations nobody planned for.
Blog posts covering this topic.
Describe a strategy in plain language, backtest it against historical data, and paper trade it before any capital is committed.