I always felt stock analysis should be simple enough for even a 5 yr old to understand. Not quite 5 but my 6 yr old had a field day with the new mvp looking up at stocks like McDonald’s, Walmart, target and the companies she knows. It’s https://t.co/fXSFm4aL7w btw
I showed my 8-year-old daughter (a huge Sprite fan) what Sprite looks like under a microscope.
She stared for a second and went, “Ewwww!” 🤢
Then she looked at me with the biggest smirk and said:
“Now let’s do coffee.” ☕😂
These Gen Alpha kids… they’re ruthless.
@SyedSadathull17@tanmaigo Yes slack plus Claude has its use cases. It’s single player. Context stays within the channel. Don’t know whose entitlements the claudebot is going to use to access data. PromptQL otoh solves for cases where org context is key, is multiplayer, runs with your own entitlements.
@quantumflower11@tanmaigo Whatever you connect to. It could be slack or teams or confluence or share point or whatever. More than that it creates a learning loop to extract the tribal knowledge resigning in peoples head.
@Tracyuep@tanmaigo With slack I tag Mike and ask for a report. Mike inturn tags 3 different people, compiles the report, Comes back to slack, and gives me the report. Here you ask Promptql and it gets the work done. And you can tag Mike to just review the report.
@0xAmruth@tanmaigo That’s the best part abt Promptql. U can run this in our own cloud with your own LLMs. And it works with zero copy architecture. Data stays wherever it is. So try it out
@adm_lawson@tanmaigo You actually don’t. It’s just one of the I/O surfaces. I can hook up any tool that has context of what I do. Be it slack or Teams or jira or confluence and whatnot. Sign up and try it out.
@MechanicalTwrk@tanmaigo There is documented knowledge and then there is knowledge that resides in the brain of the 30 yr experienced analyst. Extracting the documented knowledge is not the challenge. It’s extracting the tribal knowledge. PromptQL does it great with a learning loop into wiki.
@Zac_labs@michael_chomsky@akashramaiah A slightly different perspective. PromptQL doesn’t live inside slack. Slack lives inside promptql. Slack ( and Teams for that matter) are I/O surfaces for Promptql. The actual work - queries, permissions, context mgmt, governance everything happens in Promptql.
@praveenTweets@Uber it's manual context engineering that doesn't compound. The real unlock is context that captures itself, continuously, from the work itself. No engineer required. We do that pretty well at https://t.co/ZLhxWZKI9E