Most trading tools hand you a scripting language and a blank file. You write code that loops over bars, tracks state, and decides — imperatively, line by line — when to buy. Noon Barbari takes the opposite approach: you declare the conditions under which a trade should happen, and the engine works out the rest. This is a Rule grammar, not a programming language.
Declarative vs. visual scripting
Visual scripting tools — drag-a-block editors — feel friendly until your logic grows. Connections sprawl, the same condition gets duplicated in three places, and a small change means re-wiring a diagram. A declarative rule reads like a sentence: EMA(100) crosses above EMA(200) AND close > EMA(500). There is no hidden execution order, no per-bar bookkeeping you can get wrong, and no place for Look-ahead bias to sneak in — the engine only ever evaluates a rule against data that existed at that bar.
Why rules-first
A Strategy on this platform is just a structured document: which indicators it uses, the entry rules, optional triggers, the exit rules, where the stop sits, and how much to risk. Because it is data rather than code, the same definition runs identically in a backtest, in paper trading, and live. The thing you tested is the thing that trades.
The payoff: you spend your time on the part that actually carries Edge — the hypothesis — instead of debugging loop counters. The rest of this track walks through the concrete pieces, in the order you will meet them. If you want the broader theory behind any concept, the Trading 101 track covers it without reference to this platform.
Réflexion
Think of the last trading rule you tried to express in code. How much of that code was your actual idea, and how much was plumbing the language forced on you?