Trading Psychology: The One Lesson Behind a Month of Building With AI
Everyone wants one clean result. One backtest that prints green top to bottom. One test suite that passes on the first run. One confident answer from an AI assistant that settles the question so you can stop worrying about it.
We think that want is exactly backwards.
A single good result is never proof. It's a starting point. And if you stop there, you're not managing risk. You're hoping.
Why Do Traders (and Builders) Trust One Good Number?
Because one clean number feels like relief. The backtest worked, so you move on. The code shipped, so you stop testing it. Claude gave you a confident-sounding answer, so you stop asking questions.
This month we walked you through real lessons from building HTA's tools and testing our own strategies alongside Claude. Our Edge & Strategy posts told you straight. We tested 47 strategies. Zero survived full verification.
Every single one looked good at some point. A clean equity curve. A promising win rate. One number that made us want to believe...
Passing Tests ≠ A Working Tool: Our AI Trading Tool Audit Checklist
"If the tests pass, the tool works." That's the assumption almost everyone makes about AI-built software. We made it too. For about twenty minutes.
Earlier this year we had Claude build us a position-sizing guardrail tool. Something to catch us before we sized a trade too big. The first version came back looking sharp. Every test passed. The documentation read like a senior engineer wrote it on a good day. Our gut said ship it.
We didn't. And that decision is the whole point of this post.
What Was A "Perfect" Build Actually Hiding?
I (Reid) run point on our AI builds, so I was the one staring at that first version, ready to call it done. Then we did what we tell every student to do with a new strategy before it touches real money. We audited it instead of trusting it.
What we found wasn't a small bug. It was three of them, stacked underneath a shiny surface.
The tool was reading from a dead data file. A source that no longer existed in the pipeline it was supposedly checking. Run...
Building an AI Trading Risk Tool With Claude: The One Rule We Set Before Writing Any Code
Our position-sizing tool sat quiet for 30 trades before we let it touch anything. It watched real trades come in. It logged what it would have told us to do. It changed nothing.
That wasn’t caution for caution’s sake. That was the plan from day one.
This is post one in a ten-part series on what we’ve actually learned building tools and testing strategies with Claude, Anthropic’s AI. Glenn and I aren’t AI developers by trade. We’re traders who started using Claude to build things we needed and couldn’t buy off the shelf. Some of what we built worked. Some of it didn’t, until we fixed how we were building it. This series is the honest version of that process. What to do, what not to do, no polish added.
Today’s post covers the do’s. Specifically, the three things that kept an AI-built risk tool from ever putting our account in danger, even while it was still rough around the edges.
What’s the One Rule That Comes Before Any Code?
I (Reid) handle most of the AI and content systems at ...