KenKem Journal

Building systematic trading software,documented honestly

Long-form articles from the KenKem build log — what worked, what failed, and the engineering in between. Educational content, not financial advice.

The Evidence Behind MasterVP, and Where It Stops

A software engineer's honest account of how we tried to prove our own gold strategy wrong: validated first in a separate tick engine, stress-tested with the statistics built to catch luck, attributed to the one thing it actually does well, and disclosed down to the year it failed. Evidence, not a track record.

#systematic-trading#volume-profile#backtesting#risk-management#research-method#xauusd

Why Backtests Lie, and How a Tick Engine Fixes It

A software engineer's plain-language account of a defect hiding in most retail backtests: the bar-level fill assumption. Why a candle-based engine quietly flatters your results, what a pure tick engine does differently, and why I rebuilt mine so the tests would stop lying to me.

#systematic-trading#backtesting#tick-data#research-method#trading-psychology

The Kelly Criterion: How Much Should a Systematic Trader Risk Per Trade?

A plain-language walkthrough of the Kelly criterion, the formula that converts a trading edge into a position size, why betting beyond it mathematically guarantees ruin, and why practitioners run fractional Kelly instead.

#risk-management#kelly-criterion#position-sizing#systematic-trading#expectancy

The Calmar Ratio: Why I Judge a Strategy by Its Worst Drawdown, Not Its Best Month

A software engineer's plain-language explanation of the Calmar ratio, what it measures, why systematic traders often trust it over Sharpe, and why maximum drawdown is the number that actually decides whether a trader survives their own strategy.

#risk-management#calmar-ratio#drawdown#systematic-trading#trading-psychology
Chat