Why I Built a No-Code Backtesting Engine (And What I Learned About Anti-Repainting)
I'm a trader and full-stack dev. I spent 5 years trading Forex, got funded on FTMO, lost it all when market conditions changed. The one thing that could have saved me? Proper backtesting before goi...

Source: DEV Community
I'm a trader and full-stack dev. I spent 5 years trading Forex, got funded on FTMO, lost it all when market conditions changed. The one thing that could have saved me? Proper backtesting before going live. The problem is, backtesting tools suck for non-coders. TradingView requires Pine Script. MetaTrader requires MQL. QuantConnect requires Python/C#. If you're a visual trader using SMC/ICT concepts, you're stuck manually scrolling through charts bar by bar. So I built Backtrex - a no-code backtesting platform where you drag visual blocks instead of writing code. The anti-repainting problem nobody talks about Here's something I discovered while building the backtesting engine: most indicators repaint and nobody warns you about it. Repainting means an indicator changes its past values based on future data. Your backtest shows a perfect entry signal, but in live trading that signal never existed at that candle. Your backtest is lying to you. Common offenders: Zigzag indicators - they redr