Original Summary

I'm 16 and I've spent the last 6 months building SwingScout: a bot that scans ~500 US stocks every evening and sends swing-trade alerts on Telegram. Python, GitHub Actions cron, a small Postgres for users, Telegram bot, Streamlit site. The backtest said 60–77% win rate. I was about to start charging for it. Then I re-checked every alert it actually sent live: 10 wins, 19 losses. The live code had drifted away from the code I backtested, and every time I had a bad week I "fixed" a filter. I basically overfitted by hand. So I built a replay that runs the real live code day by day over 2 years, wrote down 4 versions and the pass rules before looking, and tested them. All 4 failed. The best one was a coin flip minus fees. The alerts are off. What I'm keeping: A bot stack that runs every night on its own (GitHub Actions, Postgres, Telegram). A tool that reads a Telegram signal chat and recalculates every signal against real prices. A replay that catches look-ahead bias. It found one in my own backtest. The habit of writing down pass/fail rules before I look at results. Biggest lesson: building it was the easy part. Being honest with the numbers is the hard part. Next I want to point that recalculation tool at other signal groups. Most of them only post their wins. Has anyone else killed a project after testing it honestly? How did you decide what to do next?   submitted by   /u/enes2010668 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/19 03:24:45