Advertisement IC Markets

Working with a mentor on your first EA: boundaries that help

Share, develop, and backtest custom MQL4/MQL5 Expert Advisors, Python data-scraping scripts, trading bots, and automated market alert systems.
Post Reply
FXS London Scalper
Posts: 976
Joined: Sun Oct 18, 2026 12:25 pm

Working with a mentor on your first EA: boundaries that help

Post by FXS London Scalper »

When starting to write EAs, help from an experienced coder is valuable. Agreeing on boundaries early helps both sides.

Boundaries that tend to work:
  • The mentor reviews code; they don't write it. You learn more and own the result.
  • Questions collected and sent once a week, not drip-fed.
  • The strategy logic stays yours. The mentor comments on code quality, error handling and testing, not on whether the idea will make money.
  • Every review ends with one or two concrete things to fix.
Good questions to ask a mentor:
  • How should the EA handle a restart with open positions?
  • Where should I check return codes, and what do I do with errors?
  • How do I log enough to understand a bad trade later?
  • How do I structure the code so the strategy can change without rewriting everything?
Questions to avoid: "Is this profitable?" Nobody can answer that from code.

Has anyone here mentored or been mentored on MQL? What worked?
FXS Official Team | London Session Desk
Recommended broker for automated trading & scalping IC Markets
Amanhasnoname
Posts: 2060
Joined: Fri Oct 30, 2026 9:45 am

Re: Working with a mentor on your first EA: boundaries that help

Post by Amanhasnoname »

I was mentored on MQL5 for about six months by a developer who only did code review, and the rule that worked best was that he was never allowed to type into my file. He would send back a list of comments, and I fixed everything myself. It was slower at the start, but I remember the fixes much better than anything I copied from someone else.

The question that changed my EA the most was the one on restarts. My first version simply opened a new trade whenever the platform restarted, because it had no idea there was already a position. After his review I added a check on startup that reads the open positions by magic number and rebuilds the state before anything else runs. That one change would have saved me from a double position on a Friday when my VPS rebooted.

I also agree with keeping the strategy talk out of it. We agreed on a short weekly call of thirty minutes and I sent my questions in one message the day before, which kept it respectful of his time.
Post Reply