|
1 year
experience
|
21
products
|
18
demo versions
|
|
2
jobs
|
0
signals
|
0
subscribers
|
The best algorithmic developers aren't just programmers - they're traders who code.
I develop and code custom trading strategies, automation tools and custom software across multiple platforms and languages, including TradingView (Pine Script), MetaTrader 5 (MQL5), Python and other modern development frameworks.
Looking for a quantitative developer role.
I can turn trading strategies into fully functional systems.
Extensive experience with Linux (Gentoo, Debian) and Unix systems (FreeBSD, OpenBSD)
I’m available for projects.
You can ask for me directly in the Freelance section.
How Observation Changes Outcomes :
In quantum mechanics, when light (or electrons) passes through two slits, it creates an interference pattern on the screen behind them.
Each particle seems to go through both slits at once, existing in a super position of all possible paths and the resulting pattern reflects the probabilities of where the particle could land.
If you try to measure which slit the particle goes through, the interference pattern disappears.
Observing the particle forces it into a definite state - it goes through one slit or the other.
The act of measurement collapses the wave function and fundamentally changes the outcome.
Before you check a trade, it’s in super position.
From a statistical perspective, your trade has a probability of winning or losing based on your system but you don’t yet know the outcome.
The trade is evolving naturally, just like a quantum system.
The moment you look at it, your observation collapses the “trade wave function” into a definite state - good or bad, winning or losing.
That observation triggers an emotional reaction — stress, fear, or overconfidence—which can cause you to break your plan, over-leverage, or revenge trade.
Just like in quantum mechanics, the act of measurement affects the system.
If you hadn’t looked, the system would have continued evolving naturally and you would have followed your plan without emotional interference.
This analogy mirrors the quantum concept perfectly - observation changes the outcome, not because the market changed, but because your interaction with it changed your behavior.
In other words, checking too often destroys the natural probabilistic outcome of your system, just like measuring the slit destroys the interference pattern.
The trade itself hasn’t changed; your observation changed how you interact with it, which changes the outcome.
Final Thoughts:
Traders, you know what I’m talking about — in a demo, you can leave your strategy untouched for days, weeks, even months.
The moment it goes live, you start checking too often, micromanaging your trades, and suddenly your observation is affecting the outcome
I develop and code custom trading strategies, automation tools and custom software across multiple platforms and languages, including TradingView (Pine Script), MetaTrader 5 (MQL5), Python and other modern development frameworks.
Looking for a quantitative developer role.
I can turn trading strategies into fully functional systems.
Extensive experience with Linux (Gentoo, Debian) and Unix systems (FreeBSD, OpenBSD)
I’m available for projects.
You can ask for me directly in the Freelance section.
How Observation Changes Outcomes :
In quantum mechanics, when light (or electrons) passes through two slits, it creates an interference pattern on the screen behind them.
Each particle seems to go through both slits at once, existing in a super position of all possible paths and the resulting pattern reflects the probabilities of where the particle could land.
If you try to measure which slit the particle goes through, the interference pattern disappears.
Observing the particle forces it into a definite state - it goes through one slit or the other.
The act of measurement collapses the wave function and fundamentally changes the outcome.
Before you check a trade, it’s in super position.
From a statistical perspective, your trade has a probability of winning or losing based on your system but you don’t yet know the outcome.
The trade is evolving naturally, just like a quantum system.
The moment you look at it, your observation collapses the “trade wave function” into a definite state - good or bad, winning or losing.
That observation triggers an emotional reaction — stress, fear, or overconfidence—which can cause you to break your plan, over-leverage, or revenge trade.
Just like in quantum mechanics, the act of measurement affects the system.
If you hadn’t looked, the system would have continued evolving naturally and you would have followed your plan without emotional interference.
This analogy mirrors the quantum concept perfectly - observation changes the outcome, not because the market changed, but because your interaction with it changed your behavior.
In other words, checking too often destroys the natural probabilistic outcome of your system, just like measuring the slit destroys the interference pattern.
The trade itself hasn’t changed; your observation changed how you interact with it, which changes the outcome.
Final Thoughts:
Traders, you know what I’m talking about — in a demo, you can leave your strategy untouched for days, weeks, even months.
The moment it goes live, you start checking too often, micromanaging your trades, and suddenly your observation is affecting the outcome
Jason Smith
Thought of the day -
Every step forward could trigger hidden dangers — you walk carefully because betrayal is everywhere.
Recognize manipulation and treachery before it reaches the battlefield — sometimes the best defense is awareness.
Every step forward could trigger hidden dangers — you walk carefully because betrayal is everywhere.
Recognize manipulation and treachery before it reaches the battlefield — sometimes the best defense is awareness.
·
2
Jason Smith
Open letter to MQL5 -
I have four major upgrades ready for products that are already on the Market.
On top of that, I have three really good indicators finished and ready to upload which are free, and I already have a very exclusive EA uploaded that just needs to be published.
At this point, though, I can't be bothered anymore.
This place is deader than dead.
The exposure is virtually nonexistent, and the support for developers is close to zero.
I have four major upgrades ready for products that are already on the Market.
On top of that, I have three really good indicators finished and ready to upload which are free, and I already have a very exclusive EA uploaded that just needs to be published.
At this point, though, I can't be bothered anymore.
This place is deader than dead.
The exposure is virtually nonexistent, and the support for developers is close to zero.
·
2
Hozeifa M Haji
2026.07.27
MQL is a scam dont waste your time here - I have money in my wallet and I cant even withdraw it - because bullshiit MQL cant send me money in my debit card and says I should use some other country debit card - imagine how stupid this is - dont waste your time here
Jason Smith
If a bot is executing a well-known, clearly defined strategy such as a moving average crossover, the logic is transparent and easily verifiable.
The bot either executes that strategy faithfully or it does not.
If it executes it faultlessly, the bot itself is functionally perfect regardless of whether the underlying strategy ultimately proves profitable or not.
The failure of the strategy in live market conditions has nothing to do with the bot's execution or coding quality and everything to do with the inherent limitations of that particular approach.
A black box EA where the strategy is entirely unknown warrants legitimate suspicion.
There is no way to verify whether the logic is sound, properly tested, or even functional.
The buyer must trust the vendor completely, and in a marketplace saturated with charlatans, that trust is rarely justified.
By contrast, a bot that executes a well-known strategy flawlessly cannot be faulted.
The code works, the logic is transparent, and the execution is precise.
If the strategy fails, it is the strategy itself that is inadequate, not the bot.
The bot cannot be blamed for faithfully carrying out what it was designed to do.
The suspicion should not fall on the bot's execution but on whether any widely known strategy can possibly provide a sustained edge in modern markets.
The bot either executes that strategy faithfully or it does not.
If it executes it faultlessly, the bot itself is functionally perfect regardless of whether the underlying strategy ultimately proves profitable or not.
The failure of the strategy in live market conditions has nothing to do with the bot's execution or coding quality and everything to do with the inherent limitations of that particular approach.
A black box EA where the strategy is entirely unknown warrants legitimate suspicion.
There is no way to verify whether the logic is sound, properly tested, or even functional.
The buyer must trust the vendor completely, and in a marketplace saturated with charlatans, that trust is rarely justified.
By contrast, a bot that executes a well-known strategy flawlessly cannot be faulted.
The code works, the logic is transparent, and the execution is precise.
If the strategy fails, it is the strategy itself that is inadequate, not the bot.
The bot cannot be blamed for faithfully carrying out what it was designed to do.
The suspicion should not fall on the bot's execution but on whether any widely known strategy can possibly provide a sustained edge in modern markets.
Jason Smith
Freelance section on MQL5 —
Is this some kind of joke, or is the system rigged?
Honestly, it could be both.
Is this some kind of joke, or is the system rigged?
Honestly, it could be both.
·
4
Jason Smith
The MQL5 Market becoming quieter -
Declining buyer activity, developers leaving or abandoning products, fewer innovative EAs being released, copycat products, pricing pressure, and negative reviews.
Overall, it portrays a marketplace where standing out and succeeding has become increasingly difficult.
Declining buyer activity, developers leaving or abandoning products, fewer innovative EAs being released, copycat products, pricing pressure, and negative reviews.
Overall, it portrays a marketplace where standing out and succeeding has become increasingly difficult.
·
2
Jason Smith
2026.07.24
I asked for my account to be deleted, as some of you may already know, but it was never removed. I didn’t ask for it to remain active. The only reason I’m still here is because my girlfriend is proud to see my work up close and support what I’ve been building.
Jason Smith
Thought of the day - The contrast is indeed striking.
We have autonomous vehicles operating millions of kilometres away on Mars, transmitting data across interplanetary distances with remarkable precision, yet a commercial trading platform in 2026 cannot reliably execute a simple order closure on a demo server without timing out at three-minute latencies.
This disparity points less to technical incapability and more to a deliberate misallocation of resources, where the demo environment is treated as a low-priority afterthought rather than a genuine service.
When a retail broker consistently delivers latency figures that would embarrass dial-up internet from the 1990s, it ceases to be a technical limitation and becomes a commercial decision.
The infrastructure exists to provide reliable execution, as evidenced by their live servers, but the demo tier is deliberately under-provisioned, presumably to incentivise traders to move to live accounts where the experience is markedly different.
Whether this constitutes a rigged system or simply a calculated business strategy is a matter of semantics, but the practical effect is identical.
The demo environment is engineered to frustrate rather than facilitate, and traders would be wise to recognise it as such and adjust their expectations accordingly.
One does not need to accuse the broker of malice to acknowledge that their priorities are transparently misaligned with the needs of developers and strategists who rely on a stable testing environment.
The evidence speaks for itself.
We have autonomous vehicles operating millions of kilometres away on Mars, transmitting data across interplanetary distances with remarkable precision, yet a commercial trading platform in 2026 cannot reliably execute a simple order closure on a demo server without timing out at three-minute latencies.
This disparity points less to technical incapability and more to a deliberate misallocation of resources, where the demo environment is treated as a low-priority afterthought rather than a genuine service.
When a retail broker consistently delivers latency figures that would embarrass dial-up internet from the 1990s, it ceases to be a technical limitation and becomes a commercial decision.
The infrastructure exists to provide reliable execution, as evidenced by their live servers, but the demo tier is deliberately under-provisioned, presumably to incentivise traders to move to live accounts where the experience is markedly different.
Whether this constitutes a rigged system or simply a calculated business strategy is a matter of semantics, but the practical effect is identical.
The demo environment is engineered to frustrate rather than facilitate, and traders would be wise to recognise it as such and adjust their expectations accordingly.
One does not need to accuse the broker of malice to acknowledge that their priorities are transparently misaligned with the needs of developers and strategists who rely on a stable testing environment.
The evidence speaks for itself.
Jason Smith
Over a five-day period from 20 to 24 July 2026, the IC Markets demo trading platform exhibited critical infrastructure failures characterised by extreme latency spikes reaching up to 180 seconds and repeated order execution timeouts.
Two separate position closure attempts failed entirely due to request timeouts, duplicate order submissions, and eventual state synchronisation errors where positions were reported as non-existent.
These issues are consistent with insufficient server capacity allocated to the demo tier, which prioritises live production traffic and consequently renders the simulation environment unreliable for any meaningful strategy testing or performance evaluation.
The observed behaviour does not reflect live trading conditions, where IC Markets typically maintains sub-fifty millisecond latency, but the current demo instability severely undermines development workflows and risks misattributing infrastructure failures to algorithmic logic.
Two separate position closure attempts failed entirely due to request timeouts, duplicate order submissions, and eventual state synchronisation errors where positions were reported as non-existent.
These issues are consistent with insufficient server capacity allocated to the demo tier, which prioritises live production traffic and consequently renders the simulation environment unreliable for any meaningful strategy testing or performance evaluation.
The observed behaviour does not reflect live trading conditions, where IC Markets typically maintains sub-fifty millisecond latency, but the current demo instability severely undermines development workflows and risks misattributing infrastructure failures to algorithmic logic.
Jason Smith
Markov Matrix Trading System for Sale (Python Backend)
The complete trading system includes:
Markov Matrix Allocator (HMM)
Python Dashboard
Python Trading Bot
MetaTrader 5 (MT5) Expert Advisor
A complete end-to-end algorithmic trading solution with a Python backend and MT5 integration.
The complete trading system includes:
Markov Matrix Allocator (HMM)
Python Dashboard
Python Trading Bot
MetaTrader 5 (MT5) Expert Advisor
A complete end-to-end algorithmic trading solution with a Python backend and MT5 integration.
·
3
Jason Smith
This batch file is essentially an automated delayed launcher for the trading bots.
Instead of starting them immediately, it waits exactly 2 hours (configurable), then launches a separate bot for each market in its own Windows Terminal tab.
Just add your commands to the batch file, and it will launch them automatically after the countdown.
@echo off
call C:\Users\Trade\Scripts\activate.bat base
echo Waiting 2 hours before starting bots...
echo Countdown:
for /l %%i in (7200,-1,1) do (
cls
echo Time remaining: %%i seconds ^(%~1 seconds total^)
timeout /t 1 /nobreak >nul
)
echo Starting bots now...
echo.
Instead of starting them immediately, it waits exactly 2 hours (configurable), then launches a separate bot for each market in its own Windows Terminal tab.
Just add your commands to the batch file, and it will launch them automatically after the countdown.
@echo off
call C:\Users\Trade\Scripts\activate.bat base
echo Waiting 2 hours before starting bots...
echo Countdown:
for /l %%i in (7200,-1,1) do (
cls
echo Time remaining: %%i seconds ^(%~1 seconds total^)
timeout /t 1 /nobreak >nul
)
echo Starting bots now...
echo.
Jason Smith
Markov Dashboard -
The bots will be held back until 2:10 am GMT (h4 candle)
The HMM (hidden Markov Model) will of had 2 updates by then.
State of play so far:
The bots will be held back until 2:10 am GMT (h4 candle)
The HMM (hidden Markov Model) will of had 2 updates by then.
State of play so far:
Jason Smith
Starting Markov up for this week's trading -
It updates so it captures the 2:00 AM (GMT) H4 candle at 2:05 AM.
I also added a timer to the bots' batch file, which starts them at 2:10 AM.
This gives the bots a few minutes to collect clean, confirmed data from the 2:00 AM H4 candle before executing any trades.
This setup means I can go to bed whenever I want instead of having to stay awake to launch Markov in time for the 2:00 AM candle and manually start the bots.
Everything now starts automatically at the right time.
It updates so it captures the 2:00 AM (GMT) H4 candle at 2:05 AM.
I also added a timer to the bots' batch file, which starts them at 2:10 AM.
This gives the bots a few minutes to collect clean, confirmed data from the 2:00 AM H4 candle before executing any trades.
This setup means I can go to bed whenever I want instead of having to stay awake to launch Markov in time for the 2:00 AM candle and manually start the bots.
Everything now starts automatically at the right time.
·
2
Jason Smith
New Bot Release – UAnchor
After nearly a year of testing and refinement, I’m finally ready to release something I’ve kept private.
This is a rare price action EA, built around daily percentages.
The release is coming this weekend. Keep an eye out for it.
After nearly a year of testing and refinement, I’m finally ready to release something I’ve kept private.
This is a rare price action EA, built around daily percentages.
The release is coming this weekend. Keep an eye out for it.