|
no
experiencia
|
2
productos
|
0
versiones demo
|
|
0
trabajos
|
0
señales
|
0
suscriptores
|
Most of my work is on code somebody else wrote: an EA that behaves differently live than in the Strategy Tester, an indicator that repaints, a TradingView/Pine strategy that has to run in MetaTrader. I read the existing code and report what I found before I change anything.
Recent audit: 55,000 lines of trading code, 9 critical defects found — including a live execution path that silently differed from the backtested one.
What I check by default, because this is where robots quietly lose money:
• lot size normalised to the symbol's min/max/step, so orders aren't rejected
• stop distance validated against the broker's stop level
• logic gated on bar close, not every tick, so tester and live agree
• every order result checked by retcode, never assumed
• netting vs hedging behaviour stated explicitly
I work on: Forex and metals EAs · indicators and panels · MT4 to MT5 and Pine to MQL5 conversion · risk modules (position sizing, daily loss limits, prop-firm rules) · Python-MetaTrader bridges and data export · walk-forward validation and honest statistics.
I verify numbers independently: I export the terminal's own data and recompute the result in Python/pandas, so a disputed indicator value has a second, independent calculation to compare against rather than my word.
I have also built production trading infrastructure for Binance Futures in Python — order execution, rate-limit control, a two-level kill switch, and an event-sourced backtester where backtest and live run the same code.
I trade myself, so I read a specification the way the person who will run the robot reads it — and I will tell you if something in it is going to cost you money.
I do not sell or promise profitable strategies. I write the code that executes yours, and I say so in writing before we start.
I agree the specification in detail before starting, show progress at every stage, and deliver documented code.
MQL5 · MQL4 · C++ · Python/pandas · Strategy Tester · Git
Indicator Signal Alerts Kb es la versión gratuita de alertas de Indicator Signal Trader Kb. Supervisa un indicador que ya utilizas y te avisa cuando dicho indicador emite una señal de compra o de venta: mediante una ventana emergente, una notificación push en la aplicación móvil de MetaTrader y un correo electrónico. Se pueden añadir hasta cuatro indicadores más que actúen como filtros para confirmar cada señal. No abre operaciones. La dificultad habitual con este tipo de herramientas es saber
Indicator Signal Trader Kb convierte las señales de un indicador que ya utilizas en operaciones o alertas. Tú eliges el indicador, le indicas al programa cuál de sus búferes significa «Comprar» y cuál «Vender», y configuras el stop loss, el take profit y el tamaño del lote. Se pueden añadir hasta cuatro indicadores más que actúen como filtros para confirmar cada señal. No se necesita saber programar. La dificultad habitual con este tipo de herramientas es saber qué valor corresponde a cada