pull down to refresh
166 sats \ 1 reply \ @gmd OP 30 Nov \ parent \ on: Mathematics AI Aristotle proves 30 year old Erdos Problem #124 AI
Semi live now although haven't publicly shared the URL anywhere (this is the first ever). It's an automated AI driven Technical Analysis tool for degenerate stock market gamblers like me to figure out "what's on sale". Basically helps you buy the dip when you have dry powder (sacrilegious for Bitcoiners, I know! 😂)
https://stockdips.ai/
Last night I was working on implementing concurrent background jobs to perform the LLM calls to execute the Technical Analysis across a large batch of stock tickers. Not only did it code it up for me (not one-shot but close) but it threw up a beautiful dynamic html UI that let me track the job queue in real-time! I thought it would just give me some dirty println text logs to peruse...
Gave me mixed emotions of sadness and wonder.
Looks pretty cool. And SN "launch" is wild! I'm not much into TA or stock markets so I can't really comment on the product itself. I've felt that since TA influences market behavior and TA at the same time references market sentiment then, if a specific analysis gains traction it becomes self-fulfilling - for
speculation, not long-term investment of course.About the process: what this looks like is that you're evolving a tool to automate something you'd do manually (i.e. doing the TA) and then building that out into a suite.
Not only did it code it up for me (not one-shot but close) but it threw up a beautiful dynamic html UI that let me track the job queue in real-time!
The problem with skipping the
println stage is of course that you now need to test not only the batch process itself, but also the fancy UI, and you're testing both at once. Thus, because it didn't give you the simple interface, you now have more work at once. This is fine if you didn't plan on doing rigorous testing of course.reply