logoalt Hacker News

solaire_oa • today at 9:48 PM • 2 replies • view on HN

I installed it, I tried the examples, it works.... But forgive my lack of imagination... what is this useful for?

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?

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).


Replies

devttyeu • today at 10:09 PM

I have a lot of semi-practical examples of how you can use this model wrapped in unix-ish tools - https://github.com/aurorainfra/grev (readme links to docs of each tool with some more or less practical examples)

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.

➕ show 2 replies
motoboi • today at 10:11 PM

Is for when you want an AI to make a decision. If you have been using gpt or claude or open source models for that, than it’s a way cheaper alternative.

And if you have not been, it’s for when you have to extract the context from text. When you have numbers or fixed options, it’s just a matter of code.

So if you find yourself having to decide if a given user comment is a refund_request, that’s for that.

It’s not perfect, you still have to fine-tune (or calibrate) using examples you have (and keep those examples updated over time). But it’s way better than trying to parse text with regexes.

➕ show 2 replies