Start here
Risk management for algo traders
A trading system is only useful when its position size and drawdown rules are clear enough to survive a bad run.
Read articleBlackPeak / Knowledge
A practical knowledge base for algorithmic traders. Learn how to evaluate a system, manage risk, set up MT5, and ask better questions before putting capital at risk.
Clear guides on backtests, expectancy, drawdown, and the parts of a strategy report that deserve scrutiny.
Position sizing, prop-firm limits, and operational checks come before chasing a headline win rate.
Each page has a discussion space so support questions can grow into a useful trader community over time.
Library
Start here
A trading system is only useful when its position size and drawdown rules are clear enough to survive a bad run.
Read articleResearch basics
Profit factor and win rate are useful clues, not a verdict. Learn which parts of a report deserve your attention.
Read articlePractical guide
A clean installation prevents many problems that look like strategy problems but are actually symbol, connection, or configuration issues.
Read articleFoundations
An MT5 Expert Advisor is software that turns a defined trading process into repeatable decisions and orders.
Read articleProcess
A useful journal records more than wins and losses: it helps you separate strategy behaviour from operational mistakes.
Read articleResearch process
A repeatable research process turns a trading idea into a testable hypothesis instead of a collection of indicators.
Read articleValidation
Learn how rolling in-sample and out-of-sample windows reveal whether an algorithm survives beyond the period that shaped it.
Read articleReal-world trading
Small trading costs compound. Here is how to measure the difference between a clean backtest and a real MT5 fill.
Read articleEvaluation accounts
Before running automation in an evaluation, translate the firm's current rules into checks your setup can actually enforce.
Read articleOperations
Automation needs an operating environment. Use this checklist to catch connection, restart, and monitoring failures before they affect a position.
Read articleStrategy families
These two strategy families respond to different market behaviours. Understanding the difference helps you choose honest tests and expectations.
Read articleMarket conditions
Economic releases can change spread, liquidity, and execution. Learn how to decide whether a strategy should trade through them.
Read articleFoundations
Understand bids, asks, market orders, pending orders, and why an algorithm's decision is only the start of a trade.
Read articleFoundations
Learn what a bar really represents and why session boundaries, timezones, and incomplete candles matter to an EA.
Read articleResearch basics
Turn a vague market belief into a precise, falsifiable question that an algorithmic research process can test.
Read articleStrategy design
Indicators transform price and volume into measurements. Learn how to use them without confusing a formula with an edge.
Read articleStrategy design
A complete strategy is more than an entry condition. Map every transition from signal to position close before coding.
Read articlePerformance analysis
Learn why the average trade, dispersion, streaks, and tail outcomes matter more than a single headline percentage.
Read articlePerformance analysis
Read common trading metrics together so one attractive number cannot hide an unstable or expensive system.
Read articleRisk management
Translate losing streaks into account-level consequences and understand why recovery requires more than the percentage first lost.
Read articleRisk management
Compare fixed lots, fixed cash risk, volatility sizing, and account-based sizing before selecting a rule your broker can support.
Read articlePortfolio design
Two bots can look diversified by name while taking the same macro risk. Learn how to measure shared exposure before combining systems.
Read articlePortfolio design
Build a portfolio from distinct return drivers, not a pile of bots that all respond to the same market move.
Read articleStrategy research
Use market conditions to understand where a system works without building a fragile switch that only recognises the past.
Read articleData engineering
Bad timestamps, duplicated bars, missing sessions, and inconsistent symbols can create an edge that exists only in the dataset.
Read articleData engineering
Match the data resolution to the strategy's decisions so the backtest does not invent precision the live system cannot use.
Read articleData engineering
A practical process for finding the data defects that silently change signals, session filters, and backtest outcomes.
Read articleResearch hygiene
The fastest way to improve a backtest is often to accidentally use information that would not have been known at the time.
Read articleValidation
Freeze the rules, protect the holdout, and evaluate the strategy in a way that resembles how it will face the future.
Read articleRobustness
Use resampled trade sequences and perturbed costs to explore how much of a backtest depends on a favourable path.
Read articlePython & tooling
Keep data, experiments, reports, and production candidates separate so your research can be reproduced months later.
Read articlePython & tooling
A reproducible backtest gives the same answer from the same inputs and makes disagreements easier to diagnose.
Read articleEngineering discipline
Use commits, experiment notes, and configuration hashes to know exactly which code produced a trading result.
Read articleEngineering discipline
Small automated tests can catch sizing, stop, time, and state errors before they reach an account.
Read articleEngineering discipline
A bot that cannot explain its state is difficult to trust. Design logs that help you distinguish no signal from no execution.
Read articleArchitecture
Explicit states make order handling, restart recovery, and protection logic easier to reason about than scattered flags.
Read articleExecution
Choose order types based on the strategy's priority: participation, price control, breakout activation, or risk protection.
Read articleMarket microstructure
A strategy can be profitable on paper but untradeable at its intended size. Learn how liquidity changes the result.
Read articleExecution research
Use observed spread and activity to decide when a strategy should trade, rather than relying on a fixed clock alone.
Read articleOperations
Latency matters differently for a scalper, a session system, and a slower swing EA. Measure the path before paying for speed.
Read articleTrade management
Exit logic controls the trade distribution, account exposure, and operational behaviour. Design it as carefully as the entry.
Read articleProtection
Build account-level brakes that remain active when the strategy is wrong, the market is abnormal, or the operator is away.
Read articleOperations
A compact dashboard should answer whether the terminal is alive, what risk is open, and why the system is or is not trading.
Read articleMachine learning
ML can help with classification, ranking, or regime description, but it does not remove the need for clean data and honest validation.
Read articleMachine learning
Create useful features from trading data while keeping the future out of the input and the live pipeline reproducible.
Read articleMachine learning
Use rolling training and validation windows to test whether an ML pipeline adapts without learning from the future.
Read articleMachine learning
Choose a model target that maps clearly to a decision, and measure whether it improves the trade process after costs.
Read articleMachine learning
Sometimes a clear rule, better data, or better execution solves the problem more reliably than a model.
Read articleDeployment
A staged checklist for moving from a promising backtest to a monitored system without skipping the uncomfortable evidence.
Read articleProcess
Build a post-launch review that separates statistical variation, execution drift, and genuine strategy failure.
Read articleTroubleshooting
A step-by-step operational diagnosis for silent Expert Advisors, from connection and symbol checks to signal and protection state.
Read articleMT5 setup
Tick value, point size, volume steps, trading sessions, and stop levels can differ across brokers even when the symbol name looks familiar.
Read articleOperations
Make session filters, daily loss resets, and research timestamps consistent across brokers, data feeds, and local displays.
Read articleProcess
Treat every input change as a new experiment so a live system does not drift away from the evidence that justified it.
Read articleBrowse by topic
Position sizing, drawdown controls, and surviving losing streaks.
How to develop, validate, and challenge an algorithmic edge.
Installing Expert Advisors and keeping the execution environment healthy.
The core concepts every algo trader should understand.
Drawdown limits, automation policies, and evaluation constraints.
Data quality, testing design, walk-forward analysis, and stress tests.
Spreads, slippage, fills, sessions, and real-world trade mechanics.
Repeatable review habits that separate evidence from emotion.
VPS uptime, monitoring, logs, alerts, and operational discipline.
Combining systems, managing correlation, and allocating risk across a portfolio.
Research notebooks, reproducible experiments, code quality, and useful tools.
Features, labels, leakage, validation, and realistic uses of ML in trading.
Liquidity, order types, order books, impact, and the mechanics behind fills.
Collecting, cleaning, aligning, and versioning the data behind a research process.
Architecture, testing, state management, debugging, and maintainable trading code.
Expectancy, attribution, robustness, drawdown, and post-trade diagnosis.
Avoiding false discoveries with clear hypotheses, baselines, and honest validation.
Ask a setup question, share a backtest, or compare notes with other algorithmic traders. Use a display name; your email remains private.
Create an account or sign in above to join the conversation.
Loading discussion…