ricericerice

It's not like Claude's subscription is super clear, either. All of these pricing models are a bit too opaque for my taste.

Indeed, while struggling with VCS is a right of passage for any tech company, I'm not sure why what they described couldn't have been built as a diff/patch API in front of git.

just tell them to point their agents at it /s

you have no idea how bitwarden works, do you...

by that logic, every time you send a password over a TLS connection, you're publishing it outright too

you can easily finetune your own*

*if you have a sufficiently sized and quality dataset for the specific classifications you're targeting

I found the egregious LLM generated text a bit of a turn off, too.

If you don't care about your website, why should I?

got a link to a laptop that can run K3?

i think you underestimate how much you "just getting it" stems from being terminally online - this is a HN model release thread after all

my feeling is you're most likely wasting money using Opus for implementation. The plan and task breakdown should be specific enough that Sonnet can implement without you noticing a difference.

How do you verify in practice then? Wouldn't you need the original prompt so you can reobtain the likely token distribution to validate again the random key(s)?

After some research, I think I understand what you're getting at here - BERT being a model for encoding text but not architecturally feasible to generate text with it, which "LLMs" (the lack of definition here is resulting in you two talking past eachother), maybe more accurately referred to as GPTs, can do.

Also the irony of your comment when it in itself was confidently stated yet void of any content was not missed either - consider dropping the superiority complex next time.