forex-scalping.com

PTScalper wrote:Fairman wrote: Sun Aug 23, 2026 11:48 pm PTScalper wrote: Sat Aug 22, 2026 9:29 pm 2. cTrader (C#) cTrader doesn't have "Scripts" in the exact same way MetaTrader does. Instead, it uses cBots.

Exponential growth talk is how challenge ads are written. On a desk I care about survival of R and rule compliance. Compounding comes after the process is boring.

Prop accounts that chase the curve usually meet the trailing DD first.

How do you keep growth talk out of the session plan?

I also log refused tickets so flat time counts as work — otherwise the desk invents activity.

I would rather log a refused ticket than invent activity for the journal.

I write the walk-away before London so it is not negotiated mid-tape.

Topic note from my sheet for t=12187: keep risk unchanged until the sample says otherwise.

PTScalper wrote:PTScalper wrote: Sat Aug 22, 2026 9:29 pm 2. cTrader (C#) cTrader doesn't have "Scripts" in the exact same way MetaTrader does. Instead, it uses cBots.

I agree with this, with one caveat about where the value actually comes from.

For me, programming paid off most in the unglamorous jobs: an alert fifteen minutes before each high-impact release, a script that writes every fill to a file with the spread at the time, a check that refuses an order if the size is bigger than planned. None of that is a signal, but together it removed more mistakes than any indicator I've written.

The trap runs the other way. Once you can code, it becomes very easy to generate a hundred variations of a strategy and keep the one with the prettiest backtest. Fairman's scepticism earlier in the thread is fair from that angle: code amplifies whatever process you already have, broken parts included.

Since this thread started with an auto-lot compounding script, I'd add that risk code deserves more testing than entry code. A bug in an entry rule costs you a bad trade. A bug in position sizing, such as reading balance instead of equity or a lot step that rounds up, costs you on every trade and grows as the account grows.

So my advice to anyone starting out: build a logger first and a strategy second.