Code Is No Longer a Constraint - by Lodestone Trading

The Autonomous Trader

SubscribeSign in

Code Is No Longer a Constraint<br>"In theory, there is no difference between theory and practice. In practice there is." - Yogi Berra

Lodestone Trading<br>Jul 06, 2026

Share

I rebuilt part of my backtesting engine last month. The first time I wrote it, years ago before ChatGPT, it took the better part of three weeks. This time, with Claude Code, it took an afternoon. A few cycles of careful prompting and review, and the new version was better than the original.<br>For an operation like mine, code used to be the constraint. Not the only one, but a binding one. The sheer volume of plumbing code that a solo operator had to write, the effort needed, and systems maintenance was what stood between an idea and a running system. That pain is mostly gone now thanks to AI coding. The model code, the broker glue, the infrastructure that holds the whole thing together: most of the lines of code I once snorted are a weekend’s work for anyone with AI tools and the sense to use them.<br>That’s worth saying plainly. If code isn’t what constrains a trading operation anymore, then it’s worth writing about what does.

Subscribe

The build is a few weeks now

A senior quant who knows what they’re doing, paired with current AI coding tools, can stand up a working end-to-end MVP for a systematic equity stack in four to eight weeks. A signal model, a factor model, a backtester, broker integrations, data feeds, paper trading, a monitoring dashboard. Running. End to end.<br>That number is a guess from my own experience, not a benchmark. The direction isn’t in doubt. The plumbing that used to be hard for a solo operation is now mostly tractable for one person and a capable model. The stack isn’t the thing standing in the way anymore.<br>What constrains trading now

Several things still separate that prototype from a system you’d put leverage behind. Here’s the honest part: none of them is a wall that keeps a determined, smart, funded competitor out. They’re all technically surmountable. They’re also… expensive, slow, or both, and none of them gets cheaper because your tooling improved. The constraints shifted. They didn’t go away. They come in two kinds.<br>Task-based constraints

These include data, production exposure and validation. AI takes a lot of the grunt work out of these and leaves an tractable residual volume of work. The size of the residual determines the size of the constraint on trading.<br>Data

A complete, point-in-time-correct history is a procurement and hygiene problem that costs money and time. You have to account for:<br>Survivorship

De-listings

Corporate actions

Lookahead bias (the system cheats in backtests)

It’s wonderful that agentic coding compresses the cleaning grind, and not by a little. Point an agent at several vendors, have it cross-check corporate actions, flag the gaps, and generate adversarial tests that check whether anything references a fact dated after the as-of date. A lot of what I used to call manual work is now a monitored loop. The residual after agentic coding of a data cleaning pipeline: the time and effort you need to spend checking its work and iterating.<br>The real question here isn’t how much work an agent can reduce when it comes to cleaning financial data. It’s whether it’s sound to launch a data system that no human audited, with real capital riding. Someone needs to sign off, and that someone is accountable. Whether the agent can do the work is beside the point. Nobody ships on the strength of work they didn’t check, because the agent doesn’t lose the money when a silent error reaches the tape. Your firm does. Verification isn’t a step you finish and hand off. It’s a judgment that must be owned, which makes this less a data problem than a risk one. More on that below.

Subscribe

Production exposure

The bugs that hurt you most only show up once the system is alive: running against a real broker, in real markets, for real time. Tests won’t catch them. Keep a barrage of unit and integration tests anyway, because skipping them is indefensible now that AI writes most of them for you. But tests cover the failures you thought to imagine. The bugs that hurt are the ones you didn’t. A few from my own catalog:<br>Callbacks from the broker that sometimes silently never fire

The socket your broker de-authorized because it decided to

The malformed fill response at the close

That’s the broker deviating from orderly behavior, in undocumented ways. Some you can catch in paper trading. Some you can’t. You can shrink the rest with shadow runs and replayed message logs. But you can’t drive it to zero through prompting. At some point the only teacher is time on the tape with money behind it, and that time doesn’t compress. AI is great at fixing each bug once you’ve found it. Finding them, and building the logging that lets you see them, is the part that stays slow.<br>Validation you trust

AI will scaffold the validation for...