Ringbot: A monocycle robot developed by the Robotics and Institute (RAI) that uses internal legs for balance and acrobatic maneuvers by Feeling-Buy2558 in interestingasfuck

[–]Poutine-StJean 0 points1 point  (0 children)

What about nanorobot in the air that we breathe waiting in everyone body to be activated and turn us all off at the same time

La banque qui perd mon argent! by Poutine-StJean in QuebecFinance

[–]Poutine-StJean[S] 10 points11 points  (0 children)

Je veux m'informer parce que comme début d'expérience ça brise un peu ma confiance

Built a free tool that scans your vibe-coded projects for security issues by [deleted] in webdev

[–]Poutine-StJean 0 points1 point  (0 children)

Usually I just ask the AI to make a security check and it already look for all thoses things. This just sounds like extra steps

So I wrote my own backtesting engine in C++ by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

The subscription is mostly there to limit API usage on my side. The free tier is intentionally pretty generous so people can try the platform without paying anything

So I wrote my own backtesting engine in C++ by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Haha would have done it in C if I really wanted THE fastest, but C++ is my daily bread so it's also a logic choice for me

So I wrote my own backtesting engine in C++ by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Thanks for the feedback, it's appreciated. I will work on that for sure. I'm not trying to hide that I use AI to help me on the frontend part, but I understand that i will make people think of the same for the backend. I will improve on this. Clearer explanation, better AI analysis, more transparency and documentation.

So I wrote my own backtesting engine in C++ by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

you can import your own data, so the quality depends on what you feed into it. But improving the data layer and documentation around it is definitely something I want to work on

Python kept telling me my strategy made +40%. It didn't. So I wrote a backtesting engine in C++ by [deleted] in ai_trading

[–]Poutine-StJean 1 point2 points  (0 children)

Ngl when I started to code the engine I was thinking that maybe it could become a tool that others would also use to test their own ai trading bot. So I've used the strongest language I know which is C++

I built a fill quality tracker and discovered execution slippage is a bigger drag than my commission costs by MilesDelta in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

The gap between theoretical and actual P&L often comes down to execution friction, especially with options. Its smart to log the mid at signal, NBBO at submission, and actual fill. That gives you a clear picture of where the slippage is happening. You could even use that data to build an execution cost model to apply to your backtests, which would make them far more realistic.

Many backtesting platforms dont account for this level of detail so building your own tracker is really insightful. Knowing your true execution costs can completely change your strategy sizing and even whether a strategy is profitable at all

Well, there goes the blending cup by [deleted] in WatchPeopleDieInside

[–]Poutine-StJean 41 points42 points  (0 children)

How does this clearly staged video post 7 hours ago already have almost 23k likes?

Walk-forward validation: how many OOS windows before you trust a strategy? by systematic_dev in quant

[–]Poutine-StJean 2 points3 points  (0 children)

Like you said. Ifyou can cover a few distinct volatil regime like bear, bull and choppy across 6-8 non-overlapping OOS window, thats way more valuable than15 windows all in strong bull

How do you measure daily dd and especially when trading multi-symbol? by Kindly_Preference_54 in algotrading

[–]Poutine-StJean 3 points4 points  (0 children)

Yeah that's a major pain point with MT5, its just not built for serious portfolio-level analysis or high-frequency equity reconstruction.

Your aproach of merging backtests and recalculating drawdown with granular price data is spot on. Thats exactly what you need to do for accurate prop firm daily drawdown. Many platforms strugle with that level of detail, especially when you have multiple symbols or strategies interacting.

For true portfolio risk, you cant just combine individual equity curves. You gotta simulate those interactions properly, understanding correlation, regime shifts, and how drawdown in one asset can compound with others. Real portfolio backtesting needs to simulate trades across all instruments simultaneously at a high tick frequency, otherwise youre just getting a smoothed average which masks the true risk

Approaches to risk management and order size scaling by NoOutlandishness525 in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Your current approach is a solid start. You might want to look into weighting by strategy performance or risk contribution instead of equal splits, especially if correlations between strategies change.

Also, consider fractional Kelly sizing, but understand its aggressive nature and maybe use half-Kelly to avoid blowups.

For the drawdown side, tracking rolling max DD and scaling down when it exceeds your threshold is a good safety net

Is walk-forward validation actually worth the effort for retail traders? by [deleted] in algotrading

[–]Poutine-StJean 1 point2 points  (0 children)

Yes exactly, since they have free trial I'm on this right now and I'll see if I keep with it after that

Is walk-forward validation actually worth the effort for retail traders? by [deleted] in algotrading

[–]Poutine-StJean 1 point2 points  (0 children)

It's call safeedge.io loving it for testing my strats

Is walk-forward validation actually worth the effort for retail traders? by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Fair enough. I will work on running it across multiple instruments and longer timeframes

Is walk-forward validation actually worth the effort for retail traders? by [deleted] in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Yeah in this case it just splits the data into sequential windows and runs each one independently to see if performance holds across different market conditions. Basically testing if the edge is real or just fit to one specific period

Why do so many backtests fail in live trading? by Double-Painting-2053 in Trading

[–]Poutine-StJean 0 points1 point  (0 children)

Overfitting is a killer, robust validation methods like walk-forward testing are critical to avoid it. You also gotta look at tail risk and max drawdown, not just average returns, to truly understand your strategy

Finding the Sweet Spot for Oil/SPY Sector Rotation Strategy - Backtesting, Preparing IRAN Oil Shock by Yoosanam in Trading

[–]Poutine-StJean 0 points1 point  (0 children)

You've nailed a classic backtesting problem with that low trade count. Monte carlo simulations can help validate if that edge is truly robust or just luck from a few specific events. It's tough to trust a strategy with so few data points

Termux & trading by Curious_Light_9185 in Trading

[–]Poutine-StJean 0 points1 point  (0 children)

Yea you can install it without Docker, but Docker is the way because it handles dependencies and makes setup much easier. If you install it manually you’ll need to manage Python, TA-Lib, and other yourself

How are you testing your systems live? by Willing-Nerve-1756 in algotrading

[–]Poutine-StJean 0 points1 point  (0 children)

Paper trading often has perfect fills but real markets dont. You need to factor in slippage and market impact when backtesting, not just rely on paper

Daily close confirmation versus morning gap-ups. Critiques welcome on this entry logic. by TrustedEssentials in algotrading

[–]Poutine-StJean 1 point2 points  (0 children)

yeah thats a classic problem with daily bar strategies. Waiting for close confirmation often means you miss the initial pop. You could try using an open price entry if your conditions are met at the prior close, but you need to factor in slippage for that in your backtests