Remix.run Logo
▲ Not Everything Needs an LLM(newsletter.posthog.com)
105 points by speckx 9 hours ago | 43 comments
▲socketcluster 5 hours ago | parent | next [-]

It is true that they don't tend to give simple answers.

But it reveals something about human biases that we tend to seek out simple answers to complex questions. We tend to think that because a question is short, that it's simple. We forgot how many details are involved and how much is actually going on underneath. Reality itself is often annoyingly complex.

All living creatures, including humans, are conditioned to simplify extremely complex things into simple concepts which we can react to. We only understand things to the extent that we believe they affect us.

▲goodmythical 4 hours ago | parent | next [-]

That's just a caloric efficiency thing, isn't it?

Far easier to simply spread peanut butter and jelly on bread than to consider how the peanuts were harvested, how many bugs were in the fruits, how close the wheat was to molding, how much sugar is in the bread, how many years it tooks us to perfect such tasty and long lasting ingredients, what potenitally substandard conditions the labor involved endured...etc, every time one wants a sandwhich.

And then a multiple of that easier as well in conversing about a peanut butter and jelly sandwhich as few if any of the parties will think about any of the above.

We see the same in computers. A web dev can make it quite far without once considering the OSI model. A game dev can complete an entire career without ever worrying about the underlying bytecode.

There are situational benefits to diving deeper, of course, but I don't imagine we'd make it very far if we had to reinvent the universe for every word in every conversation or chain of thought.

▲jvanderbot 38 minutes ago | parent [-]

Calorie, bit also speed of decision and easier transmission to peers and kiddos.

A quick rhyme encoding a useful heuristic? They'll remember that for generations!

▲proc0 3 hours ago | parent | prev [-]

Simple answers are the result of a problem being solved all the way through. It abstracts away all the details and exposes the essential part of the solution. This is the compression perspective of intelligence. We want things as compressed as possible because it's how intelligence more or less works.

▲b3ing an hour ago | parent | prev | next [-]

Problem is tech is full of PMs and other managers that don’t know technology. Things that could be algorithms, functions, programs, regex filters, etc are now LLMs because they don’t know anything else to solve problems

▲cookiengineer an hour ago | parent [-]

> Problem is tech is full of PMs and other managers that don’t know technology. Things that could be algorithms, functions, programs, regex filters, etc are now LLMs because they don’t know anything else to solve problems

Is this the right approach though?

Computers should be usable by humans, not the other way around. How CPUs are built, how assembler came to be, how programming languages came to be... ultimately, they were all just compromises along the way to make computers more usable by humans.

With LLMs, however, the threshold barrier for being able to modify and use a computer effectively is now zero, which in my opinion is a good thing.

I can recommend watching "the mother of all demos" talk from 1968 [1] which basically established the design patterns for modern computers. That's how old the concept of desktop environments is. There hasn't been any meaningful invention eversince, apart from touchscreens/smartphones, and now LLMs as a generalized interface design.

[1] https://www.youtube.com/watch?v=yJDv-zdhzMY

▲TacticalCoder 6 minutes ago | parent | prev | next [-]

> A probability score of 0.85 still means ~150 wrong answers per 1,000 checks, so plan ahead for false positives and false negatives.

But that's only true if we believe the value of 0.85 in itself is correct!? For all we know it could be 0.75 or 0.9 no?

If were to make calls to something like JEV and know that the probability the answer is correct is, say, 0.85193847098713, wouldn't that be even more amazing than JEV and LLMs themselves!?

I'm not being facetious here: how do we know it's 0.85 and neither 0.75 nor 0.9?

And if 0.85 is "correct", why stop there? Why not 0.85193847098713?

Any explanation is very welcome.

▲throwawayffffas 2 hours ago | parent | prev | next [-]

Using these decision models as a model router sounds really bad to me the models will most likely be newer than the decision model and thus the decision model will have no information about the capabilities of the model other than the short blurb you feed it.

▲dzink 5 hours ago | parent | prev | next [-]

PostHog should not be using them on customer data, period.

▲jakeydus 5 hours ago | parent [-]

Every time one of these consumer data brokers/gatherers shows some insight into how they gather the data it makes me feel sick. I know they're doing it, I know it's granular, it's still gross.

▲nixosbestos 4 hours ago | parent | next [-]

Gathering it and pumping it all through Anthropic and OpenAI data collectors.

▲goosejuice 4 hours ago | parent | prev [-]

I mean look at what they sell. Surveillanceware.

▲dominotw 3 hours ago | parent [-]

postslop

▲bryanhogan 2 hours ago | parent | prev | next [-]

Hearing about use cases for decision models and seeing how they are being explored is quite interesting, but I think the title of this post is poorly chosen.

▲vibebingo 2 hours ago | parent | prev | next [-]

> What is the current conservation status of hedgehogs?

A harnessed LLM can look this up using tools.

Maybe LLM at least ti prepare context for decision model.

I guess if using a decision model context prep is key.

▲saejox 4 hours ago | parent | prev | next [-]

I have been using structured json outputs since gpt 4 days. Never understood this jev hype

▲acedTrex 4 hours ago | parent [-]

i think the main deal is speed right?

▲triMichael 2 hours ago | parent [-]

No, the main deal is that it CANNOT answer with anything outside the given structured options. LLMs can go off the rails, however small a chance it is. The architecture behind JEV and the like doesn't let it do that.

▲j16sdiz 25 minutes ago | parent [-]

> structured json outputs

▲fauria 4 hours ago | parent | prev | next [-]

Related: Amazon saves millions by replacing Sonnet 4.6 with Strands Decider - https://news.ycombinator.com/item?id=50436640

▲CharlesW 3 hours ago | parent [-]

As I understand it (and count that I will be proven wrong if not), Strands Decider is an LLM, just a discriminative example instead of a generative one.

▲fauria 2 hours ago | parent [-]

Strands Decider is an open source decision model like Jev, they serve the same purpose.

▲CharlesW 2 hours ago | parent [-]

Right, so still an LLM, but with the generative bits replaced with a decision probability generator. Yes? https://www.microsoft.com/en-us/research/publication/llm2jev...

▲dieselgate 5 hours ago | parent | prev | next [-]

Completely unrelated to the article itself but I landed on the posthog.com homepage after viewing their open positions and the landing page is cool. It's sort of a desktop UI and different from what I usually see, was expecting some other HR domain to come up.

▲aabdi 5 hours ago | parent | prev | next [-]

Contrarian take. I think everyone should use LLMs and the most expensive possible, unless they know how to run evals (both on line and off line).

Yes its expensive, ugly, etc. But...

I've seen enough IRL that people just create really bad evals that do not reflect real world. Then the product is just bad. Outright broken for the p90 customer.

People don't know statistics. Offline Evals are hard. Sampling the entire population distribution is hard. Sampling the fat tail is harder. Online evals are big ops projects that are giant balls of death.

▲abhgh 4 hours ago | parent | next [-]

Maybe I should write up a post about this, but about evals ... I have feelings. Yes you're right that writing evals is hard. And it comes down to the simple fact that the thing that you're testing - a LLM-driven feature that presumably suffers from variance and inadequate accuracy - and your measuring device - an LLM judge - suffer from the fundamental problems. But the lure of natural language is such that instead of seeing this pipeline of LLM-driven things as a path of cascading errors, it is easy to view it as one set of problems correcting for another set.

In this world, the LLM-driven feature is a probabilistic entity, and the judge layered on top of that is another probabilistic entity. The real work is to look at the judge's response and infer the performance of the feature. Good evals make the inference step "pass-through", i.e., the judge outcomes have a 1:1 mapping with feature outcomes. But this kind of reliability often doesn't naturally appear. I think of reliability as being composed of three attributes: (a) consistency: do we get the same result for an eval run on the same llm with the same input (b) inter-llm agreement: do outcomes agree over multiple trials of running an eval over multiple llms with the same input (c) accuracy: does the eval agree with human judgement. You need extra work to guarantee these properties. And even when you can, you won't get 100% reliability, but say high 90s, and you still to make a judgement call as to call a feature "functional".

▲aabdi 3 hours ago | parent [-]

Two things, my problem isn't with the probabilistic nature, its:

1. with the quality of the data that customers use to eval.

2. with the lack of rigor/ops/testing around accuracy for deployment and regression.

I'll give you examples for failures IRL:

Offline:

- sample distribution for test data didn't have p99 customers in it, failed in production when it launched for those customers.

- test data sets were all synthetic, launch to real customers fails because data set was not representative of real.

Online:

- yeah we used LLM as a judge in prod/online eval, but the judge sampling failed to measured against our japanese customers, our bilingual customers, customers with media devices etc.

- the LLM as a judge was used, but there was no measure of human accept rate measures/alarms for various use cases (lightbulbs turning off, music playing, etc) so the lightbulbs started failing.

- there was no consistent human sampling of online data, so for example samsung TVs stopped working, but no one caught it until 3 months later when some VP was watching his TV and it broke and was accelerated despite it affecting 2-3% of customers.

▲mrbungie 2 hours ago | parent | prev | next [-]

If you are not getting feedback from those p90 then your bad evals are the least of your problems.

Also, unless those p90 customers are bringing a big portion of your income (again, if that happens you'd KNOW that your product is broken for them) I'd not pay for the most expensive LLM to "avoid doing evals".

▲aabdi 2 hours ago | parent [-]

>If you are not getting feedback from those p90 then your bad evals are the least of your problems.

the feedback is part of your online evals... if you have bad feedback you have bad evals

> Also, unless those p90 customers are bringing a big portion of your income (again, if that happens you'd KNOW that your product is broken for them) I'd not pay for the most expensive LLM to "avoid doing evals".

they are but that's besides the point.

Two ways:

- logically ROI of accuracy degradation as compared to cost has to be measured, sure.

- emotionally, morally sub 10% groups in our customer distribution include such things as disabled people, minorities, and the elderly. In my view you should love all your customers.

▲dieselgate 4 hours ago | parent | prev [-]

Can you elaborate on what you mean by Eval? All I can think of is eval() in js...

I hope you agree people should use the "right tool for the job" meaning a calculator for arithmetic rather than an LLM for everything.

▲aabdi 3 hours ago | parent | next [-]

Evals are tests of model accuracy. For example here are 100 people's sample houses, go test if the agent can turn off the lightbulbs correctly.

Right job sure. But, If you're replacing the LLM with a jev like as in the article, or switching with a smaller classifier, then you better have good data/evals otherwise you're reducing accuracy without you even knowing.

▲dominotw 3 hours ago | parent | prev [-]

its basically assertEquals(x,y) where function is calling llm to check equals

▲tchalla 2 hours ago | parent | prev | next [-]

Not everything needs a "decision model" with a "system one" API either but here we are.

▲jakeydus 5 hours ago | parent | prev | next [-]

"Not everything needs an LLM! Use a decision model!"

And what is a decision model exactly? An LLM with instructions to limit responses?

Huh.

▲orbital-decay 4 hours ago | parent | next [-]

Sure it's an LLM, it's just neither generative nor instruction-tuned, like BERT (also an LLM), which gave them a reason to market it as not being one. Though modern "LLMs" are also modeling a lot more than just the language so they're kind of hard to define. Not much point in being pedantic, let them call anything anything and see what sticks.

▲amelius 4 hours ago | parent | prev [-]

Sounds like a yes/no question.

▲Rapzid 4 hours ago | parent | prev | next [-]

The approach of using decision models to gate more expensive work.. I mean, yeah.

But using protecting PII as an example use case is a bit bonkers?

▲jscd 3 hours ago | parent | prev | next [-]

I continue to be astonished that a real company exists called "post hog"

▲Terr_ 3 hours ago | parent [-]

Post hog, ergo proper hog.

▲cognitif 3 hours ago | parent | prev | next [-]

Wait, I don’t need an LLM to do arithmetic?

▲pj_mukh 4 hours ago | parent | prev [-]

tl;dr Not everything needs an LLM, but everything needs a typesafe wrapper around an LLM.

Gotcha

▲acedTrex 4 hours ago | parent [-]

Ridiculous field we are in, people seemingly have forgotten the absolute basics in under a year.

▲LtWorf 3 hours ago | parent [-]

The people doing these things never knew the basics.