I'm a developer who got curious about Al Brooks price action — and decided the best way to learn it was to code every concept from scratch, backtest it, and write honestly about what the data says.

Brooks is famously discretionary. Most argue his work can't be quantified. I'm not trying to prove them wrong — I'm genuinely curious what happens when you try.

The format

Each post covers one concept: what Brooks means by it, how I translated it into a mathematical definition, what Python backtesting showed, and — crucially — what the quantitative definition is probably missing.

That last part matters. A lot of this project is about finding the boundary between what can be systematized and what genuinely requires human judgment.

Why learn in public?

Because I learn better when I have to explain things. And because I couldn't find anyone else doing this — coding Brooks concepts one by one, showing actual backtest results, being honest about limitations.

All code is open source on GitHub. If you find a bug in my logic, open an issue.