Ask someone six weeks into an automated trading course to explain what their strategy's expectancy is in R, and the answer tells you what kind of course it was. If they can state it, along with the sample size it came from, the course taught measurement. If they describe the entry rules instead, the course taught a strategy — and a strategy without a way to evaluate it is a belief.
That is the fault line running through this whole category. Automation is not a trading style; it is the act of writing your process down in a form a machine will execute exactly. If the process is vague, automation makes the vagueness precise and expensive. A curriculum that produces competent automated traders therefore has to be built in a particular order, and it is not the order that sells best.
The order that works
Module one: measurement, before anything else
Nothing downstream is assessable without this, which is why it goes first even though it is the least exciting thing on the list.
- Expectancy expressed in R multiples, and why R makes a gold trade comparable to an index trade.
- Sample size and the honest limits of small samples. Forty trades tells you very little; slicing forty trades into four groups tells you nothing at all.
- The difference between drawdown depth, drawdown duration, and the maximum losing streak a given win rate produces.
- Why a profitable month is not evidence and a losing month is not disproof.
A trader who finishes this module and nothing else is better equipped than one who finishes everything else and skips it.
Module two: market mechanics
What you are actually trading, in units.
- Contract specifications, point and tick values, lot steps and minimum volumes.
- How a spread, a commission and an overnight financing charge each reach your account, and which of them scale with time rather than with size.
- The difference between a CFD on an index and the futures contract behind it.
- Order types, and specifically what a stop order promises and what it does not.
- What a broker does with your order, and why a fill is not the same as a quote.
This module is why the sizing arithmetic in later modules is possible. Skipping it produces traders who size by habit.
Module three: risk and position sizing
- Percentage risk from equity and stop distance, computed from the instrument's real tick value.
- Aggregate exposure, correlation, and why four positions on dollar pairs are one position.
- Drawdown limits, static and trailing, and what each does to a strategy with normal variance.
- Sizing as the primary control over gap risk, because it is the only one.
Module four: strategy construction
Only now, and deliberately framed as hypothesis rather than recipe.
- Turning a market observation into rules a machine can execute with no ambiguity.
- Entry, exit, invalidation and position management as four separate decisions.
- Regime dependence: which conditions the idea requires, and how you will know they have gone.
- Why the exit, not the entry, determines most of the distribution.
A curriculum that hands you a finished strategy has skipped the part where you learn to build and discard them, which is the actual skill.
Module five: testing without fooling yourself
The most technically demanding module and the one most often reduced to "how to press the backtest button".
- Data quality, and what tick-level, minute-level and modelled data each can and cannot tell you.
- Realistic assumptions for spread, commission, slippage and swap, and how sensitive the result is to each.
- Over-fitting: parameter counts, degrees of freedom, and why an equity curve that improves with every tweak is a warning.
- Out-of-sample and walk-forward testing, and the discipline of not looking.
- Forward testing on demo as a separate, non-negotiable stage with its own pass conditions.
Module six: execution and infrastructure
The module most courses omit entirely, and the one where deployments actually fail.
- Where automation runs: a local machine, a VPS, or a service that does not share a fate with your terminal.
- What happens on restart, reconnect, and partial failure, and why state held in memory is a bug waiting for a reboot.
- Idempotency and deduplication — the reason a reconnect must not replay yesterday's orders.
- Logging and audit: what you need recorded to reconstruct a strange afternoon three weeks later.
- Monitoring, including the question nobody asks until it matters: how will you know it has stopped.
Module seven: the journal and the review loop
- What a connected account can capture automatically and the few fields only you can supply.
- Reviewing at the right cadence — weekly for process, quarterly for strategy — and not reacting to single trades.
- Deciding in advance what would make you turn a strategy off, and writing it down before you need it.
Module eight: the operating environment
- Broker and venue selection, and how execution quality differs between them.
- Prop-firm rules where relevant: loss limits, news windows, prohibited practices, and what automation does and does not change about them.
- Tax and record-keeping, which is jurisdiction-specific and which a course should tell you to take elsewhere rather than answer badly.
TIP
Look at any course's module list and ask where testing and infrastructure sit. If they are the last two modules, or a bonus, the course is a strategy product with an automation label. Those two modules are where automated trading is actually different from discretionary trading.
Seven tests for telling a course from a funnel
The honest ones and the extractive ones use similar language, so judge on structure rather than on tone.
- 01Is the full curriculum visible before purchase? A module list with specifics is a curriculum. "Module 4: The Secret" is a funnel.
- 02Does the price appear on the page? A price that only arrives after a call is a price set by what the caller thinks you will pay.
- 03What is the upsell path? One course at one price is a product. A low entry price leading to a mentorship, then a mastermind, then a signals subscription, is a funnel where the course is the lead magnet.
- 04How are results presented? Screenshots of account balances tell you nothing about sample size, risk, or how many accounts were not shown. Look for a distribution and a trade count, or treat the claim as marketing.
- 05Does it talk about failure? Any serious curriculum spends real time on what goes wrong. A syllabus with no module on losing is not describing trading.
- 06Is there pressure on the clock? Countdown timers that reset, seats that are always nearly gone, prices that rise at midnight every midnight. This is a sales technique, and its presence is information about the seller.
- 07What is being sold underneath? If the course exists to route you towards a broker affiliate link, a signals channel, or a specific product, the curriculum will bend towards whatever makes that necessary. Check whether the teaching would still make sense with a different broker and a different tool.
WARNING
Be most sceptical where the claim is about outcome rather than skill. Nobody can promise what your trading will return, and anyone framing a course as an income route rather than an education is telling you what they are. Past results, theirs or anyone's, establish nothing about yours.
What a course cannot supply
Three things, and they are the three that decide whether the education was worth anything.
Screen time. Recognising a market condition you have read about takes repetition. There is no module that substitutes for having watched a few hundred sessions.
A loss you have actually felt. Reading about drawdown and sitting in one are different experiences, and the second is where most of the learning happens.
Your own discipline about scope. The most common failure among people who complete a course is not ignorance. It is running the third strategy before the first one had a measured sample, because the course covered three.
A reasonable self-directed order
If you are assembling this yourself rather than buying it, the sequence is the same and free versions of most of it exist. Learn to measure. Learn the instrument's mechanics in units. Learn sizing. Build one hypothesis and write it precisely. Test it honestly, including a full demo stage with pass conditions. Deploy it where it will survive a reboot. Journal it. Review it on a schedule. Then, and only then, build a second one.
Eight steps, and most people do them in roughly reverse order — which is a large part of why the failure rate in this activity is what it is.
Where this fits
For the demo stage in that sequence, run as a concrete fortnight with pass conditions, see demo-testing-protocol-for-automation. For the measurement module in practice — what a journal can capture automatically and the fields you have to supply — read automated-trading-journal-what-it-captures.
