|
nein
Erfahrung
|
0
Produkte
|
0
Demoversionen
|
|
0
Jobs
|
0
Signale
|
0
Abonnenten
|
Software Engineer | .NET | MQL5 | NinjaTrader
in
Self-employed
MQL5 Developer — Expert Advisors & Custom Indicators | NinjaTrader, QuantConnect
• I build and maintain algorithmic trading systems in MQL5 — Expert Advisors, custom indicators, and strategy backtesting/optimization.
• Coming from commercial .NET development, I focus on clean, modular, testable code. I value multi-strategy EAs with drawdown control on several levels — Portfolio, EA, and per-strategy.
• I actively develop my own trading frameworks and strategies for my portfolio relying on walk-forward backtesting with minimal optimization.
• I also build trading systems on NinjaTrader (NinjaScript) and QuantConnect, and can port strategies between these platforms and MQL5.
Portfolio CodeBase:
• https://www.mql5.com/en/code/74427 - Result type-safe error handling
Services:
• Expert Advisor development — from idea or specification to a tested, optimized build, including multi-strategy EAs with drawdown control at different levels.
• Custom indicators — building indicators from scratch and converting logic from other platforms or scripts into MQL5.
• Backtesting & optimization — walk-forward testing with minimal optimization to keep strategies robust and avoid curve-fitting.
• Cross-platform strategy porting — moving strategies between MQL5, NinjaTrader (NinjaScript) and QuantConnect.
• Refactoring & fixing existing code — debugging, restructuring and improving EAs and indicators written by others.
How I work:
I treat trading systems as real software, not throwaway scripts. My code is built on a modular architecture — thin adapters over the MQL5 API and reusable domain objects (position sizing, stop-loss, risk rules) — so strategies stay clean, readable and easy to extend or maintain.
• Modular by design — clear separation between API adapters, domain logic and strategy code, so components are reusable across EAs.
• Risk-first — drawdown and exposure control built in at Portfolio, EA and per-strategy levels, not bolted on afterwards.
• Tested & robust — walk-forward backtesting with minimal optimization to avoid curve-fitting.
• Engineering discipline — a commercial .NET background brings version control, clean code and maintainable structure to every project.
• I build and maintain algorithmic trading systems in MQL5 — Expert Advisors, custom indicators, and strategy backtesting/optimization.
• Coming from commercial .NET development, I focus on clean, modular, testable code. I value multi-strategy EAs with drawdown control on several levels — Portfolio, EA, and per-strategy.
• I actively develop my own trading frameworks and strategies for my portfolio relying on walk-forward backtesting with minimal optimization.
• I also build trading systems on NinjaTrader (NinjaScript) and QuantConnect, and can port strategies between these platforms and MQL5.
Portfolio CodeBase:
• https://www.mql5.com/en/code/74427 - Result type-safe error handling
Services:
• Expert Advisor development — from idea or specification to a tested, optimized build, including multi-strategy EAs with drawdown control at different levels.
• Custom indicators — building indicators from scratch and converting logic from other platforms or scripts into MQL5.
• Backtesting & optimization — walk-forward testing with minimal optimization to keep strategies robust and avoid curve-fitting.
• Cross-platform strategy porting — moving strategies between MQL5, NinjaTrader (NinjaScript) and QuantConnect.
• Refactoring & fixing existing code — debugging, restructuring and improving EAs and indicators written by others.
How I work:
I treat trading systems as real software, not throwaway scripts. My code is built on a modular architecture — thin adapters over the MQL5 API and reusable domain objects (position sizing, stop-loss, risk rules) — so strategies stay clean, readable and easy to extend or maintain.
• Modular by design — clear separation between API adapters, domain logic and strategy code, so components are reusable across EAs.
• Risk-first — drawdown and exposure control built in at Portfolio, EA and per-strategy levels, not bolted on afterwards.
• Tested & robust — walk-forward backtesting with minimal optimization to avoid curve-fitting.
• Engineering discipline — a commercial .NET background brings version control, clean code and maintainable structure to every project.
Freunde
3
Maksym Yaroslavovych Libovych
Hat den Code Result - type-safe error handling for MQL5 without exceptions veröffentlicht
Eine kleine Bibliothek mit wenigen Abhängigkeiten, die einen „Result“-Typ im Rust-Stil in MQL5 einführt. Funktionen geben ein einzelnes „Value-or-Error“-Objekt zurück, anstatt auf den globalen Status von `GetLastError()` zurückzugreifen, sodass Fehler explizit angezeigt werden und nicht ignoriert werden können. Enthält „ResultValue“ (Werttypen) und „Result“ (Objekte, auf die über Zeiger verwiesen wird), eine „Error“-Struktur, Makros für vorzeitige Rückgabe (TRY, RETURN_ON_ERROR, …) sowie optionale „Then“-/„Match“-/„MapError“-Callbacks.
60
109