User
Write something
Pinned
Start Here!
New here? Three things to do first — the About video, the Intro course, and making an introduction post to tell us about yourself! Click for links.
0
0
Start Here!
Pinned
Welcome to the Strategy Corner!
This is where you can share your favorite trading strategies and discuss them. Please remember that we're family here, so be respectful of others and let's all have fun learning together!
0
0
Coding experience
Quick question. How much coding experience do I realistically need to make automation workable?
Volume Profile Fade — MES
I've been building this one for a while and it's finally running live on sim, so I thought I'd drop it here and see what you guys make of it. The idea is pretty simple. Price pushes out of the session value area, fails, and closes back inside. I short that close and target the point of control, with the stop beyond the extreme of the rejection. It'll only take the trade if the level it's fading lines up with something else — prior day or overnight VAH/VAL, weekly levels, a high-volume node edge. Diagram below if that's easier to look at than read. It backtested well enough that I wanted to see it on live data rather than keep tuning it, so that's where it is now. Forward test, sim only, no conclusions yet. Which is really why I'm posting. I'd love a couple of people to run it alongside me. More charts and more sessions means I get to an honest answer faster than I would on my own, and I'd rather find out it doesn't work in six weeks than six months. Things I'd genuinely like opinions on: 1) Does the confluence requirement earn its place, or did it just survive because it tested well? That one nags at me. 2) What's a fair cost assumption when the POC target is sometimes only a few points away? 3) How many trades would you want to see before you'd believe anything either way? Also worth a mention since it's a nice example of the plumbing mattering as much as the logic: I found a bug in it this week where the dashboard table was being re-merged on every tick, which Pine treats as a runtime error. The script was dying part-way through execution and the symptom showed up as wrong alert values — nowhere near the dashboard code that caused it. The fix was deleting one keyword. Finding it was not a one-keyword job. Pine's attached. It's set up for MES on the 1 minute. Run it on sim, and if you do, please shout if you see anything I've missed.
Volume Profile Fade — MES
The Renko Nibbler Three (MNQ)
This is one of my favorite strategies using renko bricks instead of candles. It runs on size 50 renko bricks on the 1m MNQ chart. The rules are simple: When three renko bricks fully paint in one direction, enter a trade in that direction. When two opposite-directions bricks fully paint, exit. It works great on trending days and you can capture big moves on MNQ. Be careful running it on slow/ranging days. Attaching screenshots as well as the pinescript, so you can try it out if you want. Please note that backtest results for renko strategies can be very misleading. As with any strategy, I would recommend paper trading this for a while before trusting it on a real account!
1
0
The Renko Nibbler Three (MNQ)
1-5 of 5
SHARQ School of Automation
skool.com/sharqschool
A community focused on stock futures strategy trade automation. No coding experience required! We use TradingView, TradersPost, and Claude!
Leaderboard (30-day)
Powered by