Quant Trading Bot Devlog

한국어로 보기

Quant Trading and Momentum Trading Weren't the Same Question

A quant trading concept I happened to revisit this morning cleared up a confusion I'd been carrying about my project's identity for a while

This is the English version of a post originally written in Korean for my algorithmic trading system devlog(new tab).

I got curious this morning. It's been a couple of months since I started using the term "quant trading" for this project, and I realized I'd never really nailed down how precisely I was using it. So I sat down and worked through the concept again.

What quant trading actually is

In one line: it's finding statistical regularities in quantitative data — price, volume, financial statements — and turning those regularities into code that trades mechanically. The core isn't "throw away intuition." It's turning intuition into something verifiable.

For example, turning the intuition "undervalued stocks eventually rise" into a testable question like "does buying the bottom percentile on some metric every month produce excess returns." Once it's phrased that way, you can actually check it against historical data.

Quant covers a lot of ground. Factor investing that picks undervalued, high-quality names. Statistical arbitrage that bets on the gap between two assets that used to move together. Trend following. Lately, machine-learning-based prediction too. What all of these share isn't "what to buy" — it's "how to decide and execute."

So is my project quant, or momentum?

Working through this brought back a question I'd been vaguely confused about for a while: is my project aiming to be quant trading, or momentum trading?

Sitting with it, I realized the question itself was off. I'd been treating the two as if they were competing choices on the same axis.

Here's where I landed. Quant is a methodology for "how to decide." Momentum is just one of several signals you can use inside that methodology. Value, which buys what's undervalued. Momentum, which buys what's recently risen. Quality, which picks names with sound financials — these are all choices about "what to treat as a signal."

Execute any of that mechanically with data and rules, and that's quant. So "quant or momentum" was never a question at the same level to begin with.

Looking back at my own project through this lens

I ran my project back through this frame. Inside the AI recommendation pipeline(new tab) there are three roles looking at the market through different lenses, and one of them reads trends and regime shifts as the market moves through time. That's closer to a momentum-style view.

But that role doesn't decide trades on its own. It produces a ranking alongside a role that reads valuation and financial data, and a role that reads news and disclosures, and the three rankings get combined into a final judgment through consensus. Momentum was never an identity this system "became" — it was already sitting there as one ingredient among several.

To be sure, I had an AI advisor double-check whether this frame actually held up for my project. The conclusion came back the same: there's no separate trading logic in this system worth calling a standalone "momentum strategy" — it's just one trend-reading signal mixed in with the others.

What the confusion actually was

Looking back, the reason I was confused was simple. I'd been putting "quant" and "momentum" on the same scale and thinking I had to pick one.

In reality they weren't on a scale at all — they were different questions. Quant answers "how." Momentum is one of several answers to "what to look at." Treating them as if they belonged in the same spot was the wrong question from the start.


It's strange how just re-deriving a concept from scratch untangled a confusion I'd been carrying for a while. Sometimes redefining the terms turns out to be a faster path than staring at the code.