• Information
12+ years
experience
13
products
573
demo versions
1
jobs
0
signals
0
subscribers
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

We firmly believe that striving for perfection is the road to excellence. With this as our keystone, barmenteros FX is devoted to providing tailored MT4 programming service (also MT5) for Forex traders worldwide. In addition to MetaTrader, we also program for other popular trading platforms as TradingView, NinjaTrader and TradeStation. With years of experience, we have improved the methods and processes that enable us to create high-quality, robust and stable programs for Forex market. We aim to create long term partnerships with our customers by exceeding expectations with a top level of professionalism, honesty, and transparency.

Reach us here: barmenteros.com
Boris Armenteros
Every indicator-based Expert Advisor has to decide which candle it reads: the one that is still forming, or the last one that closed. The same moving-average crossover or RSI threshold behaves differently depending on the answer...
Boris Armenteros
The first published schedule Until this year, MT4's end-of-life was a prediction...
Boris Armenteros
A converted Expert Advisor that compiles without a single error is not evidence that the conversion worked. The characteristic MT4 to MT5 failure does not produce anything wrong to find — it produces an absence, something that should have happened and didn't...
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
There is a conversation that repeats often enough to be worth writing down. A trader has traded a setup manually for months, decides to automate it, and frames the project as "turn my rules into an EA." The entry logic gets written in an afternoon...
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 Failure Pattern Most EA reliability discussions focus on broker edge cases, slippage, and backtest-to-live gaps. The restart failure is quieter — and it repeats on every restart. The pattern: an EA runs correctly for months on a VPS...
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
Permission to run an Expert Advisor is not what disqualifies automated prop-firm accounts. Automation permission is not where firms compete — they differentiate on payout splits, drawdown limits, and challenge fees...
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
A PPO agent trained for two million steps on EURUSD 15-minute data with flat reward curves across all five seeds is not an optimizer problem. Switching to SAC will not fix it. Changing the learning rate will not fix it...
Boris Armenteros
DRL algorithm comparisons often headline annualized return. If you plan to deploy the agent on a live MetaTrader account, that is the wrong column to sort on. Here is a benchmark that makes the point concrete...
Boris Armenteros
If you have trained a deep reinforcement learning agent in Python and tried to run it against a live MT5 terminal, you may have seen this: the agent converges cleanly, the backtest Sharpe looks good, and then on a paper account it behaves like it never trained. No error, no warning...
Boris Armenteros
Consider a Phase 1 challenge EA that is disqualified on day 9. The strategy is profitable — positive P&L at the point of disqualification. The journal tells the story: trades are opening after the daily loss limit has already been breached...
Boris Armenteros
A clean compile tells you the syntax is valid. That is the whole of its claim. It does not tell you that the correct order was selected before the close, that a rejected request was noticed, or that the Expert Advisor still knows what it holds after a terminal restart...
Boris Armenteros
The Pattern A trader runs an EA profitably for months or years. No code changes. No settings modified. The equity curve starts bleeding. The trader backtests — still shows good results. The trader re-optimizes — makes it worse...
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 4.1%. For six weeks, every trade is roughly 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...
123