Viewing profile — laalshaitaan
laalshaitaan
HN member- Joined
- Tue, Oct 31, 2023, 10:30 AM UTC
- HN karma
- 114
- Public activity
- 131 items
- HN profile
- View on Hacker News ↗
About laalshaitaan
Recent public activity
-
comment
Comment #48972747
ai slop again
-
comment
Comment #48972744
that on the customer's side to redact the PII as you are the ones sending it and you'd know better than us
-
comment
Comment #48926719
i get the push, most teams come to us after they've done/tired of the claude running analysis thing manually and want a pro-active thing. we're also targeting conversation first us…
-
comment
Comment #48924848
its fascinating how the toyota example comes up anywhere, its so good! wdym by modelling the messages and conversations though? i lose you a bit there! for the crm approach, i do t…
-
comment
Comment #48924664
a lot of our customers want a daily morning report on slack & flag things instantly rather than to wait for a week so thats why we keep it realtime
-
comment
Comment #48917732
it gets hard when you need this continuously across lots of chats/calls, with metadata, changing clusters, going deeper into a user journey, etc. the LLM call is just one part of i…
-
comment
Comment #48917699
i agree w you for smaller teams tbh. if you have a few hundred convos and someone can maintain scripts/prompts, hand-rolling is probably fine. it becomes less tiny when it’s 10k+ m…
-
comment
Comment #48916257
im hearing this for the first time and damn! i just told this to my cofounder/cto and he said hes gonna give this a shot in the coming days. damn, i read bayesian in statistics lik…
-
comment
Comment #48915316
seems ai slop
-
comment
Comment #48915302
oh gotcha, yeah happy to chat more! yeah DMing
-
comment
Comment #48915120
i love this comment bec we started as analytics for mcp servers haha! we then expanded to conversations bec thats where most mcp servers were being used lol. we havnt figured out y…
-
comment
Comment #48915096
i like these kinds of critiques, we don’t think conversation logs or analysis on top of it is alone enough to replace observability or evals. imo they answer diff questions for dif…
-
comment
Comment #48915078
yea, at our volume which we still consider small as we've been able to figure out a way with llms & embeddings, its still fine. + we onboarded a voice ai company with more than 2 h…
-
comment
Comment #48914124
okay nice, also is it safe to assume you do once a fortnight releases then? like look at the last week's data then use it for product decisions the coming week? also have you updat…
-
comment
Comment #48913851
oh damn, can you share what the skill is actually doing for you like on a daily basis: is it creating clusters, scoring known issues, or finding new patterns? and what data points …
-
comment
Comment #48913560
[dead]
-
comment
Comment #48913150
on a satirical note: we also have an mcp server/api endpoint if you dont want the ui
-
comment
Comment #48913126
we're still learning and so our the prompts haha, whats your take though
-
comment
Comment #48912523
lol i wish it was just wrapping prompts but things got harder once our customers grew bigger, we had to build queues. we had to do context management for bigger conversations and b…
-
comment
Comment #48911144
lol true but then you’re just building another us :D
-
comment
Comment #48910477
codex is great for like a one-time/overview analysis on a handful of transcripts. we usually serve to companies where the volume is >10k messages & continuous ingestions + with cla…
-
comment
Comment #48910353
haha yea, i even got the domain rageprompt dot com like a couple of days ago lol i love the name too. for profanity, did you define keywords or just let the agent figure out rage s…
-
comment
Comment #48909479
I’m gonna try and give this to my cloud agents and get a benchmark now lol
-
story
Launch HN: Agnost AI (YC S26) – Extract user feedback from agent conversations
Hey HN, we’re Shubham & Parth, childhood friends building Agnost AI ( https://agnost.ai ), product analytics for teams building chat and voice agents. We read production conversati…
-
comment
Comment #48852878
lessgooo! context dev ftw!