Ollaya – Ollama for open-source, Jev-style decision models
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Ollaya – Ollama for open-source, Jev-style decision models
Unofficial Hacker News client; not affiliated with Y Combinator.
solaire_oa · · focus · HN ↗
Like, their example is of classification for a support interface.... `refund_requested`. Pretty convenient bool given the example is about a refund- what if 99% of submissions don't ask about a refund? Also, is that user not a `churn_risk`? What could possibly qualify as a churn risk if not a user asking for a refund?
<a href="https://ollaya.dev/library/laya" rel="nofollow">https://ollaya.dev/library/laya The examples suffer the same problem of why I'd prefer to use a string column vs an enum. Changing an enum means you need to update the db, using a string you can do whatever.
I'm not trying to be negative, I genuinely want to know about some practical examples (that don't require tons of backwards maintenance).
devttyeu · · focus · HN ↗
Really I think "smart grep" is a pretty good one ('look for an error looking vaguely like this'). Also I think sql-based shell history + decision model is quite good to make the last 'which one of those choices is best fit given users past few commands' etc.
spaniard89277 · · focus · HN ↗
motoboi · · focus · HN ↗