Category: Invest

  • Teaching an AI to research stocks and poke holes in my ideas

    I had a trade idea. To evaluate it properly I needed: current price action, historical bars for technicals, macro context, and whether the company filed anything interesting with the SEC recently. Four different sources. Four different formats.

    That's a lot of context switching for one question: "Is this idea actually any good?"

    The research agent

    Give it a ticker, it goes to work. It pulls market data, computes technicals, fetches filings, and puts it all into a structured report. Technicals, fundamentals, recent filings, preliminary thesis assessment.

    No single piece of the output is amazing on its own. The technical analysis mostly tells me what I can already see on the chart. The value is seeing everything in one place. Instead of switching between six tabs and trying to hold the full picture in my head, I get a structured starting point.

    Is it as good as a professional analyst's report? No. Is it better than what I was doing before, which was "glance at a chart and go with my gut"? By a lot.

    The thesis interviewer

    This might be my favorite thing I've built. Almost didn't build it because it sounded gimmicky.

    You describe a trade idea and it asks hard questions. What's your exit plan? What if the catalyst doesn't materialize? How much are you willing to lose?

    It surfaces things I hadn't considered. Not because the AI is smarter. It's just methodical in ways that humans, especially humans excited about a trade idea, aren't. It asks the obvious questions you forgot to ask yourself because you were busy being convinced you were right.

    I haven't had a dramatic "gotcha" moment where it saved me from a terrible trade. It's more subtle than that. It forces me to articulate my reasoning, and sometimes the act of articulating it reveals how thin it is.

    The workflow

    The two tools together create a loop: start with an idea, run the research agent to build context, then run the thesis interviewer to stress-test the idea against that context. What comes out the other end isn't a recommendation. It's a clearer picture of whether the idea is worth acting on.

    Some ideas don't survive the process. That's the point.

    What I've learned about AI in trading

    If I've learned anything, it's that AI is best at synthesis and worst at judgment. Give it five sources about a company and ask for themes, and the results are solid. Ask "should I take this trade?" and it can't answer that. It doesn't know my risk tolerance or portfolio context.

    As a devil's advocate it's surprisingly effective, because it doesn't care about being right. It just pokes at your reasoning until it finds weak spots. Humans get attached to ideas. AI doesn't.

  • Why I’m building my own trading platform

    I wanted to learn Python. Tried tutorials, toy projects, the usual. Nothing stuck. I could follow along but I couldn't build anything real on my own.

    Then vibe coding happened.

    I trade on the side. Swing trades, some options, mostly based on technical signals and fundamental research that I piece together manually. The trading itself isn't the problem. The process around it is. I have a full-time job. I can't spend three hours every evening on research. But I'm trading real money, and "glance at a chart and go with my gut" isn't a system. It's a habit I haven't replaced yet.

    I'd always wanted to build a trading platform. Something that forces me to learn async programming, API integrations, all of it. I just couldn't get past the gap between "I understand the tutorial" and "I can build the thing." AI-assisted coding closed that gap. I can describe what I want, iterate on the output, and ship something real. I'm learning more about Python from building with AI than I ever did from courses.

    What I actually want

    I don't want a Bloomberg terminal or a hedge fund quant stack. I don't want a bot that trades while I sleep.

    I want a single place where I can see what's happening with the stocks I care about, test ideas against history, and track my trades honestly. Right now I don't track trades in any structured way. No journal. No system for reviewing what worked. That's a problem when you're trading real money and trying to improve.

    The honest part

    I still don't fully understand every line of code in this project. But I understand what it does, why it's structured the way it is, and how to change it. Every feature I build teaches me something. Last week it was async programming. This week it's state management. Some days it feels like building a car while learning to drive.

    But the act of building, translating a vague idea into working software, I can't stop doing that. Vibe coding didn't replace learning. It gave me a way in.

    This is going to be a series. I'll share what I'm building and what I'm learning. Eventually, the actual investment theses that come out of it.