Where to Go Next
A map of what you have learned, the parts of AFL still to explore, and how to keep getting better.
- ·What you can now build
- ·Areas to go deeper
- ·Good habits & version control
- ·The function reference
- ·Joining the community
- ·From AFL to a full workflow
Thirty-five chapters ago, AFL was a wall of unfamiliar words. Look at what it is now. You can open the Formula Editor and plot an indicator without thinking twice. You can scan an entire watchlist for a setup, turn that setup into a system with clean entries and exits, backtest it honestly, optimise it without fooling yourself, and finally take it live - reading a higher time frame, firing alerts to your phone, and routing real orders through OpenAlgo. That is the full arc of a systematic trader, and you have walked all of it.
AFL has been stretched into machine-learning datasets, options dashboards and full automation frameworks. The function reference and the trading community are where most users go to keep levelling up.
This last chapter is not a lesson - it is a map of the road ahead. Where to go deeper, the habits that keep you improving, and where to turn when you are ready for more.
What you can now build
You hold a complete workflow, and it is worth saying out loud because most people never assemble it: chart, scan, backtest, optimise, alert, automate. An idea now has a clear path from a hunch on a chart all the way to a deduped, sandbox-tested order. You are no longer guessing whether something works - you can measure it.
That loop is the real prize. Every new strategy you meet for the rest of your trading life - in a book, a forum, a video - you can now drop into this pipeline and ask the only question that matters: does it actually have an edge?
Areas to go deeper
AFL is a deep well, and we have drawn from the top of it. A few directions reward the next push:
- Portfolio backtests. We tested one symbol at a time. AmiBroker's real power is testing a whole universe at once - ranking candidates, allocating capital across many positions, and respecting a fixed amount of equity. This is where backtests start to resemble real trading.
- The custom backtester (CBT). For logic the standard backtester cannot express - dynamic position sizing, custom exit priorities, portfolio-level rules - the CBT lets you reach into the trade loop and shape it bar by bar.
- Walk-forward analysis. The honest answer to over-fitting: optimise on one slice of history, test on the next, unseen slice, and roll forward. It is the closest thing to proof that an edge is real rather than curve-fit.
- Advanced GFX dashboards and ML exports. The low-level graphics functions render professional control surfaces right on the chart, while AFL can write your indicators and outcomes to a file - the doorway from rules-based systems to data-driven ones.
Do not chase all five at once. Pick the one that fixes your current bottleneck. If your single-symbol systems work but you cannot choose between candidates, learn portfolio backtesting. If you fear your good results are luck, learn walk-forward. Let your own questions choose your next topic.
Habits that compound
The traders who keep getting better are rarely the cleverest - they are the most organised. Three habits do most of the work:
- Version-control your
.aflfiles. Keep your formulas in a folder under Git (or even dated copies). When a "small tweak" quietly breaks a working system, you will want to walk back to exactly what worked. - Keep a strategy journal. For every system, write down the idea, the rules, the backtest numbers, and - most importantly - why you believe it should work. A system you cannot explain is one you will abandon at the first drawdown.
- Test in sandbox before live. This was our standing rule and it never expires. New code goes to OpenAlgo's sandbox (analyzer mode) first, every time. Going live stays a slow, deliberate choice.
The single habit that separates lasting traders from the rest: never run untested code with real money. Sandbox first, size small, scale only when reality matches your simulation. Discipline, not brilliance, is the edge that survives.
Where to turn next
When you need the precise behaviour of a function - every argument, every edge case - go straight to the source: the official AFL function reference at amibroker.com/guide. It is the definitive manual, and learning to read it well is its own quiet skill.
You should not learn alone, either. The trading community around AmiBroker and OpenAlgo is generous - forums, groups and open-source repositories where people share formulas, debug each other's code, and trade ideas. Posting your own work, even imperfect, is one of the fastest ways to improve.
If this course gave you a taste for coding your edge and you want to go further, OpenAlgo's free Python courses at /learn are the natural next step - the same systematic mindset, applied with the broader reach of a general-purpose language for data, research and automation.
Recap
- You now own the full loop: chart, scan, backtest, optimise, alert, automate - the complete systematic workflow.
- Go deeper through portfolio backtests, the custom backtester, walk-forward analysis, advanced GFX, and ML exports - one at a time, led by your own questions.
- Compound your skill with three habits: version-control your formulas, keep a strategy journal, and always test in sandbox before going live.
- The amibroker.com/guide reference and an active community are your standing companions; /learn is where to continue with code.
You came in unable to write a single formula, and you are leaving with a system that can think, watch, alert and act. That is a real, durable skill - the kind that quietly improves every trading decision you make from here. Keep building, keep testing honestly, and keep your risk small while your ideas grow. The market will always be there tomorrow; the trader you are becoming is the part worth investing in. This is the end of the course - but only the beginning of what you will build with it. Well done, and good trading.