Thread

1. solaire_oa · 1790372935 · focus · 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?

   <a href="https:&#x2F;&#x2F;ollaya.dev&#x2F;library&#x2F;laya" rel="nofollow">https:&#x2F;&#x2F;ollaya.dev&#x2F;library&#x2F;laya The examples suffer the same problem of why I&#x27;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&#x27;m not trying to be negative, I genuinely want to know about some practical examples (that don&#x27;t require tons of backwards maintenance).

   1. motoboi · 1790374317 · focus · HN ↗

      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.

      1. [deleted] · 1790374460 · focus · HN ↗

         [deleted]

Unofficial Hacker News client; not affiliated with Y Combinator.