preloader
post-thumb

Last Update: September 13, 2026


BYauthor-thumberic

|Loading...

Keywords

Ask ten traders what the difference is between an indicator and a strategy and you'll get ten variations of "the strategy is the indicator plus some rules." Ask where the alpha is and most will point back at the indicator — a better MACD setting, a smarter RSI threshold, the right moving average pair.

After years of building and, more importantly, measuring trading systems, I've come to a different model. The three words name three different layers, with three different jobs, and three different failure modes. Most losing systems aren't built from bad indicators. They're built from a confusion about which layer is supposed to be doing which job.

An indicator is a measurement instrument

RSI doesn't have an opinion about your trade. It's a ratio of recent up-moves to down-moves, compressed into 0–100. MACD is the distance between two moving averages, and the momentum of that distance. Parabolic SAR is a trailing curve that accelerates under a trend. Bollinger Bands are a rolling mean with a volatility envelope.

That's all they are: measurements. A thermometer, not a doctor.

This framing sounds obvious, but it has two consequences people skip.

First: a measurement instrument must be correct, and you should verify it the way you'd verify a thermometer — against a reference. Indicators have canonical definitions, and real implementations drift from them more often than anyone admits. Wilder's Parabolic SAR is a good example, because it's deceptively fiddly: the update rule clamps the stop against the prior two bars' extremes, freezes the acceleration on the reversal bar, and seeds the flip at the old extreme point. Miss one of those details and you still get a plausible-looking dotted line on the chart — it hugs trends, it flips at pullbacks — but it disagrees with the canonical value on a large fraction of bars and, crucially, it flips at different times. Every strategy sitting on top inherits that error silently. We once traced a chronically underperforming trend system to exactly this: not a bad idea, a mis-measuring instrument. The fix wasn't a new strategy; it was making the thermometer read the true temperature.

The test is cheap: implement the indicator twice — once your way, once as a line-for-line port of the reference definition — run both over a few thousand bars, and demand zero disagreement. If you can't be bothered, at least diff your values against a charting platform's. A strategy built on an unverified indicator is a building inspection performed with a broken level.

Second: an indicator fires on every event, including the false ones — by design. RSI crosses 70 in every strong trend, repeatedly, all the way up. MACD crosses its signal line dozens of times in a ranging week. A Bollinger breakout bar looks identical whether it's the start of a 5% move or a one-bar fakeout. The instrument's job is to report the event, not to judge it. If you find yourself trying to tune an indicator until it "stops giving false signals," you're asking the thermometer to prescribe the medicine. Judgment is the next layer's job.

A strategy is a policy

A strategy consumes measurements and produces decisions — and the decisions are the whole game. The same MACD crossover event can anchor a dozen different strategies depending on the policy wrapped around it:

  • Context: do we act on a bullish crossover in any regime, or only when a higher timeframe agrees? A crossover on the hourly against a falling daily trend is a different trade from the same crossover with it. In our measurements, this single conditioning decision routinely swings a signal population from net-negative to net-positive — with the indicator untouched.
  • Timing versus deciding: fast timeframes are excellent at timing an entry and terrible at deciding its direction. A policy that lets a 15-minute signal pick the direction while the 4-hour trend disagrees is letting the second hand of the watch overrule the calendar.
  • Exits: two strategies with identical entries and different exits are different strategies — usually more different than two strategies with different entries and the same exits. An exit policy that snaps shut on every one-bar wobble will bleed a trend-following entry dry; an exit that only responds to its own thesis breaking will hold through noise and give back tails. Neither is "right"; each belongs to a different kind of trade, and mixing them up is one of the most expensive silent errors in system design.
  • Proportion: where is the stop, relative to the structure that justified the entry? If a breakout bar is so extended that the logical stop sits several ATRs away, the signal may be "valid" and the trade still unacceptable. A policy has to be allowed to refuse a true signal.

Notice that none of these decisions live inside MACD. You cannot fix a policy problem by re-tuning a measurement — and almost every "indicator graveyard" thread you've read is a catalogue of policy problems misdiagnosed as indicator problems.

Alpha is what survives honest accounting

So where's the alpha? Not in the indicator — everyone has RSI. Not in the strategy skeleton — crossover-plus-filter is public knowledge. Alpha lives in the mapping between what you measure and what you do, and it only counts if it survives honest measurement.

The clearest public evidence for that claim comes, ironically, from the place that industrialised the word: WorldQuant's famous 101 Formulaic Alphas paper, which published a hundred and one real production alpha expressions. Look at two of the simplest:

txt
Alpha#101:  (close - open) / ((high - low) + 0.001)

Alpha#6:    -1 * correlation(open, volume, 10)

Alpha#101 is just "where in its daily range did the stock close" — a normalized candle-body. Alpha#6 is the ten-day correlation between opening price and volume, negated. Squint and these are indicators — small, honest measurements, no more mystical than RSI. Nobody at a chart-trading forum would call them edges.

What makes them alphas is everything wrapped around the formula, which the paper's framework standardises so thoroughly it barely mentions it: each expression is computed cross-sectionally across thousands of stocks, converted to a rank, traded as a dollar-neutral portfolio — long the top of the rank, short the bottom — and rebalanced on a fixed schedule with costs accounted. The formula is layer one. The rank-long-short-rebalance contract is layer two, fixed and identical for every alpha. And because layer two never varies, layer three — the honest accounting — becomes an assembly line: thousands of candidate expressions can be measured the same way, kept if they survive, discarded or watched as they decay when the crowd finds them. WorldQuant's real invention wasn't any formula in that paper. It was freezing the policy layer so that measurement could be mass-produced.

That's the same lesson in institutional form: the expression is cheap; the mapping and the accounting are the asset. The same point shows up at retail scale with any charting indicator, and the best illustration I can offer is a study we ran on the classic Bollinger squeeze — the folklore that a breakout from unusually narrow bands is more likely to be "real." It's chart-reading orthodoxy, and every trader's eyes confirm it. We labelled about 12,000 historical band breakouts as real or failed (did the move travel a couple of ATRs before giving the break back?) and conditioned on how narrow the bands were at the break, measured properly as a z-score against recent history.

The result, in precision/recall terms:

Question
Answer from ~12,000 breakouts
Are narrow-band breakouts more likely to succeed?
No. Success rate was flat (~44%) at every narrowness threshold.
Do narrow-band breakouts travel further in absolute terms?
No. Wide-band regimes are volatile regimes; they move more points.
Do narrow-band breakouts travel further relative to their own bands?
Yes — strongly and monotonically. Deep squeezes travelled about 1.1 band-widths; bloated bands about 0.4.

Read that carefully, because it explains the folklore and the losing trades. On a chart, a squeeze breakout looks dramatic — the move dwarfs the coil that preceded it — and that relative drama is real and measurable. But a squeezed band-width is small in absolute points, so the probability of profit and the size of profit are no better. The eye is measuring in band-widths; the account is denominated in dollars.

Here's the layer lesson: the indicator (band-width) contained genuine information. Consumed as an entry filter — "only trade narrow-band breakouts" — it produced zero alpha; we swept every threshold and the precision never lifted. Consumed as geometry — sizing targets and stops in band-widths conditioned on the squeeze — the same measurement became useful. Same instrument, same numbers; the alpha appeared or vanished depending entirely on the mapping. And even then, the first mechanical implementation of the "useful" version lost money, because a target placed at the median expected travel amputates the right tail — and in trend trading, the right tail pays for everything. The measurement was right, the first policy consuming it was wrong, and only measurement told us which was which.

The accounting has to be honest

That phrase — what survives honest accounting — is doing a lot of work, so let me name the two frauds we catch ourselves committing most often.

Lookahead by timeframe. When a strategy consults a higher timeframe, the daily bar your backtest sees at 2 pm includes 2 pm's price action. Live, the completed daily bar you can actually consult is yesterday's. We once validated a higher-timeframe filter retrodictively — it separated winners from losers almost perfectly — then re-tested it with only the bars a live system could have seen. It not only stopped working; it deleted the best trade in the sample and made everything worse. The filter's "predictive power" was the trade's own outcome leaking backwards through an in-progress bar. Anything that looks like a perfect discriminator deserves suspicion in proportion to its perfection.

Sample-size theatre. Eight trades cannot validate a rule; they can only inspire one. The discipline that saved us more than once: when a small sample suggests a rule, implement it, run it against the full history through the live-path simulator, and be genuinely prepared for the answer to be no. Roughly half the time, it is no — and every "no" is a strategy you didn't bleed out on live.

There's a quieter corollary worth stating: when your test says a mechanism doesn't work, record the negative result where the code lives. Six months later, someone — probably you — will have the same clever idea, and the cheapest experiment is the one you don't re-run.

The working model

If you want the whole post in four lines:

Layer
Job
Failure mode
Indicator
Measure one thing correctly, on every bar, fakeouts included
Silently wrong implementation; tuned to "avoid false signals"
Strategy
Policy: context, timing vs deciding, exits, proportion, refusal
Policy problems misdiagnosed as indicator problems
Alpha
The edge left after honest, lookahead-free, adequately-sampled measurement
Retrodictive perfection; median targets amputating the tail; eight-trade proofs

The practical upshot is a change in where you spend effort. Most people spend it at layer one, cycling through indicators and settings. The measured reality is almost exactly inverted: verify layer one once against the canon and then leave it alone; spend your creative effort at layer two, where context and exits live; and spend your skeptical effort at layer three, where every idea — especially the beautiful ones — goes to be counted.

RSI is not your edge. What you do the third time RSI crosses 70 in a strong uptrend — and whether you ever actually measured it — might be.

Comments (0)

Leave a Comment
Your email won't be published. We'll only use it to notify you of replies to your comment.
Loading comments...
Previous Article
post-thumb

Oct 03, 2021

Setting up Ingress for a Web Service in a Kubernetes Cluster with NGINX Ingress Controller

A simple tutorial that helps configure ingress for a web service inside a kubernetes cluster using NGINX Ingress Controller

Next Article
post-thumb

Sep 11, 2026

在天矶(Tyokiie)里,重新遇见中国古典诗词

天矶(Tyokiie)现已收录《唐诗三百首》及数千首唐诗宋词——每一首都配有 AI 绘制的水墨背景,可按作者、诗名或朝代搜索,还能化作古琴意境短片。

agico

We transform visions into reality. We specializes in crafting digital experiences that captivate, engage, and innovate. With a fusion of creativity and expertise, we bring your ideas to life, one pixel at a time. Let's build the future together.

Copyright ©  2026  TYO Lab · v0.0.28