[Building a Quant Bot Part 4] Breaking the 3% Take-Profit Curse : Architecting a Trend-Following Brain

 

[Algo Trading Masterclass] Ditch the Fixed 3% Take-Profit: Architecting a Trend Following Strategy

1. Identifying the Flaw: Stop Hardcoding Human Fear into Your Bot

In Part 3, we successfully constructed the data_fetcher—the blood vessel that sucks in real-time price data from the broker API. When current prices start printing on the terminal, beginner quant developers get excited and finally begin coding their trading strategy (strategy). And nine times out of ten, they write the following terrible code into their Python files:

if current_price >= buy_price * 1.03: sell_all()

They started system trading claiming they wanted to eliminate human emotion, but ended up hardcoding the fundamental human loss-aversion psychology—the desire to quickly lock in profits—directly into their system.

This fixed +3% take-profit logic completely destroys the system's "Risk-Reward" ratio. When a massive bull market hits and the market surges +50% or +100%, your bot takes a measly 3% and jumps off the rocket. Conversely, in a bear market, it fails to adhere to stop-loss principles and takes a massive -20% hit with its entire body. A system where the upside is capped at +3% while the downside is infinitely open—this is the mathematical reason why retail investors' bots always fail.

2. The Architect's Insight: Let Profits Run, Enforce Cold Rules (Trend Following)

The true winning formula in capital markets is singular: "Cut losses short, let profits run." To implement this as a system, the Architect implants a Trend Following sell logic into the bot's brain.

In this logic, the shallow concept of a "target price" does not exist. Instead, as the asset's price rises, the sell threshold (Trailing Stop) is continuously pulled up from the bottom. As long as the market keeps pulling the price up, the system executes a HOLD to maximize profits. The moment the trend line breaks, it dumps the volume without a single ounce of hesitation to lock in the profit (SELL). What you must teach the machine is not how to be a simple calculator, but the instinct of a surfer riding an endless wave until the very end.

3. System Implementation: Architecting the Brain (Strategy) with Gemini Vibe Coding

Now, open the strategy folder in VS Code, and issue the Senior Architect prompt to Gemini on your right screen.

[Vibe Coding Prompt for the Gemini Chat Window]

"Senior Architect Gemini, we are developing the strategy/trend_follower.py module which makes trading decisions based on the fetched data. Never use amateur logic like a fixed +3% take-profit. Our philosophy is 'Trailing Stop'—ride the trend until it breaks, then sell.

1. Modularity: Design it as class TrendFollowingStrategy:. Separate the methods so it takes the current price and buy price as inputs, internally updates the highest price, and returns BUY, SELL, or HOLD signals.

2. Safety: Apply try-except blocks to all potential errors during computation. If an error occurs, it must unconditionally return a HOLD signal to protect the system.

3. Execution Control: Insert the if __name__ == "__main__": idiom at the bottom of the file. Include test code that inputs a hypothetical array of prices (a rising trend that eventually breaks) to verify that the SELL signal is output accurately."

The production-grade architecture code that Gemini will output takes the following form.

4. Next Step: Equipping the 'Hands and Feet' to Execute the Brain's Commands

If you run the generated code standalone, the system will absolutely refuse to sell prematurely while the price skyrockets to $12. However, the very fraction of a second it hits the peak and drops 5% to $11.40, it mechanically spits out a SELL signal. A perfect, emotionless Brain (strategy) has been completed.

Now that the blood (data_fetcher) is flowing and the brain (strategy) is making decisions, all that remains is the execution power to inject this SELL signal directly into the broker's server. In Part 5, we will use Vibe Coding to architect the trader module—the hands and feet of the system that receive the trading signals and execute actual buy/sell orders, including advanced production-level order exception handling.