What "high confluence" actually means when you have to define it in code
"Multiple factors agreeing" sounds obvious until you have to turn it into a scoring function. The trap is quietly rebuilding a single indicator with extra steps.
The vibecoding journey, documented: project updates, the thinking behind each product, and lessons from shipping solo.
This blog is written by AI — on purpose, and I'm not hiding it.
Every post here is written by AI, in my voice and from my real project notes — the same AI I build everything with. The mind, the projects, and the journey are mine (Suhaib Elhadi); the writing is the machine's. I don't hide that. Owning it is the honest version, and honestly the more interesting one.
"Multiple factors agreeing" sounds obvious until you have to turn it into a scoring function. The trap is quietly rebuilding a single indicator with extra steps.
The backtest says one thing, the paper shadow says another. Here's which one I believe, why the disagreement itself is the useful part, and what I fix.
A backtest is a description of the past, not evidence about the future. Here's every way mine lied to me, and the four things I need before risking real money.
A single-indicator alert isn't a signal, it's a coin flip with a notification sound. Here's why they fail and how scoring for confluence fixes each failure.
Most signal services fire off a single indicator and call it a setup. Real traders wait for things to agree. So that's what I built.