• Информация
12+ лет
опыт работы
13
продуктов
573
демо-версий
1
работ
0
сигналов
0
подписчиков
Trading dreams into real trading.

Take a look at our products here: https://www.mql5.com/en/users/barmenteros/seller

Hire us here: https://www.mql5.com/en/job/new?prefered=barmenteros

barmenteros FX is an independent team of algorithmic trading developers based in Marbella, Spain. We build, fix and migrate Expert Advisors, indicators and machine learning systems for traders and firms: on MetaTrader since 2011, and also on NinjaTrader, cTrader, TradeStation, MultiCharts and TradingView. Every project gets a fixed-price quote before work starts, every EA is tested against the edge cases that break live systems, and you receive the compiled files and the full source code.

Small, well-defined jobs are welcome too: fixes, indicators, simple EAs.

Reach us here: barmenteros.com
Boris Armenteros
An EA running double risk for six weeks Consider an XAUUSD Expert Advisor whose risk input reads 2% per trade. The actual exposure per position is 3.75%. For six weeks, every trade is nearly double the intended size. The formula compiles, passes backtest, and runs live without a single error...
Boris Armenteros
Three failure patterns recur in AI-generated EAs. The code compiles clean and backtests well. It fails in production because it misses the conditions that only exist when real money is on the line...
Boris Armenteros
The Pattern That Costs You Money Most EA project overruns come from revision cycles, not from complex strategy logic. Specification quality predicts project cost more reliably than strategy complexity. Here is a typical example. A brief says: "Entry when price crosses the level...
Boris Armenteros
The curve-fitting trap in Strategy Tester optimization If you have optimized an EA in MetaTrader's Strategy Tester, you have probably done this: defined parameter ranges, hit Start, waited for thousands of combinations to finish, then sorted the results by profit factor and picked the top row...
Boris Armenteros
The check that feels like a lock Most of us started here. You want to stop your EA from running on accounts that didn't pay, so you drop something like this near the top of OnInit() : int OnInit() { long allowed = 12345678; // the buyer's MT account if(AccountInfoInteger(ACCOUNT_LOGIN...
Boris Armenteros
If you develop for clients — or you are a trader commissioning tools — you have met this request: "Remove the repainting from my indicator. Should be quick, right?" One line, priced by the requester at one day of work...
Boris Armenteros
There's a moment in every MT4-to-MT5 move where the terminal reports "0 errors" and it feels like the job is done. It isn't. A clean compile only tells you the syntax converted...
Boris Armenteros
The standard migration advice goes like this: rename the file, resolve the compile errors — most of which are renamed functions — and run the backtester. If the equity curve looks similar, you are done...
Boris Armenteros
The same five hardcoded assumptions cause the same failures on every new symbol. They are all correct on EURUSD and all wrong on everything else. Here is what breaks, why, and the runtime queries that fix each one...
Boris Armenteros
Every March and October, the same production failures surface in EA support channels: session filters that worked perfectly start letting trades through at the wrong hours...
Boris Armenteros
The same five structural gaps often hide inside a "working" EA. This is not about strategy logic. The strategies are often fine. The failures are in the plumbing: error handling, state management, environment assumptions, execution validation, and defensive guards...
Boris Armenteros
I use AI daily for MQL4 and MQL5 development — scaffolding functions, writing boilerplate, exploring implementation approaches. The pattern is clear: AI-generated code works reliably on closed, mechanical problems and fails on open-ended ones where the market is the test environment...
Boris Armenteros
A clean backtest proves your entry and exit rules. It does not prove your EA will survive a live night. Those are two different things, and the gap between them is where most EAs quietly fail at 2am. The backtester feeds your code a tidy, sequential stream of ticks. Every order fills...
Boris Armenteros
A clean recompile is where an MT4-to-MT5 migration starts, not where it ends. The functions rename, the errors clear, the Strategy Tester runs — and four architecture differences sit underneath, none of which throws an error...
Boris Armenteros
If you are migrating from MQL4 or debugging a position management bug you cannot reproduce in Strategy Tester, read this before changing anything else. What the Documentation Actually Says The MQL5 reference for `CTrade::PositionClose()` is technically accurate. Both overloads are listed...
Boris Armenteros
Every EA project starts with a brief. The brief describes entry conditions, exit logic, position sizing, and timeframe. It is usually thorough on paper. In practice, it is almost never complete...
Boris Armenteros
The Silent Failure Mode Running two or more expert advisors on the same MetaTrader account exposes a structural gap that single-EA backtesting never reveals. The platform logs no warning when one EA modifies or closes an order it doesn't own...
Boris Armenteros
Whether a struggling EA deserves targeted optimization or a full rebuild comes down to three structural factors: code structure quality, strategy logic validity, and state management architecture. This is the decision a code review has to make, and the answer is never obvious from the outside...
Boris Armenteros
The Problem Picture an EA rescue brief like this: excellent single-trade backtest results, inconsistent live performance during periods when two or more positions run simultaneously. The root cause can be a single function call — `AccountBalance()` in the lot-size function...
Boris Armenteros
Оставил отзыв на заказчика за работу Gorilla Forex Group Terminator
123