Live data from Hacker News

Things we learned about LLMs in 2024

simonwillison.net

121–130 of 615 posts

Re: Things we learned about LLMs in 2024

#121
post #62
post #9

I'd love to read a semi-technical book on everything that we've learned about what works and what does not on LLMs.

It would be out of date in months. Things that didn’t work 6 months ago do now. Things that don’t work now, who knows…

Do you mean performance that was missing in the past is now routinely achieved?

Or do you actually mean that the same routines and data that didn't work before suddenly work?

Re: Things we learned about LLMs in 2024

#122

Earlier quoted context omitted.

Been in the Mac ecosystem since 2008, love it, but there is, and always has been, a tendency to talk about inevitabilities from scaling bespoke, extremely expensive configurations, and with LLMs, there's heavy eliding of what the user experience is, beyond noting response generation speed in tokens/s. They run on a laptop, yes - you might squeeze up to 10 token/sec out of a kinda sorta GPT-4 if you paid $5K plus for…

I have a 2023 mbp, and I get about 100-150 tok/sec locally with lmstudio.

Which models?

Re: Things we learned about LLMs in 2024

#124
post #50
post #37

Spookily good at writing code? LLMs frequently hallucinate broken nonsense shit when I use them. Recognize what they do well (generate simple code in popular languages) while acknowledging where they are weak (non-trivial algorithms, any novel code situation the LLM hasn't seen before, less popular languages).

Did you try learning HOW to get good code out of them? As with all things LLM there's a whole lot of undocumented and under appreciated depth to getting decent results. Code hallucinations are also the least damaging type of hallucinations, because you get fact checking for free: if you run the code and get an error you know there's a problem. A lot of the time I find pasting that error message back into the LLM gets…

Like all AI simps, your blanket response to pointing out flaws is to tell me to do more prompt engineering and then dismiss the issue entirely. In the time it takes me to coax the model to do the thing I was told it knows how to do, I could just do the task myself. Your examples of LLM code generation are simple, easy to specify, self-contained applications that are not representative of software you can actually build a business on. Please do something your beloved LLMs can't and come up with an original idea.

Re: Things we learned about LLMs in 2024

#125
post #54

About "people still thinking LLMs are quite useless", I still believe that the problem is that most people are exposed to ChatGPT 4o that at this point for my use case (programming / design partner) is basically a useless toy. And I guess that in tech many folks try LLMs for the same use cases. Try Claude Sonnet 3.5 (not Haiku!) and tell me if, while still flawed, is not helpful. But there is more: a key thing with L…

yeah, they save as much time as finding a template with a good old search and using it.

Re: Things we learned about LLMs in 2024

#126
post #65

I think John Gruber summed it up nicely: https://daringfireball.net/2024/12/openai_unimaginable OpenAI’s board now stating “We once again need to raise more capital than we’d imagined” less than three months after raising another $6.6 billion at a valuation of $157 billion sounds alarmingly like a Ponzi scheme — an argument akin to “Trust us, we can maintain our lead, and all it will take is a never-ending stream of…

According to the internal projections that The Information acquired recently they're expecting to lose $14 billion in 2026, so that record breaking funding round won't even buy them 6 months of runway at that point even by their own probably optimistic estimates.

Re: Things we learned about LLMs in 2024

#127
post #87

Earlier quoted context omitted.

Hopefully things have narrowed but you can see from the trends data just how few people (API may be a different story) use claude relative to chatgpt.

Brand awareness is a hell of a drug.

Indeed, although I find myself reaching for o1 more than Claude for matters other than programming, solely because it has better LaTeX (...)

Re: Things we learned about LLMs in 2024

#128
post #50

Earlier quoted context omitted.

Did you try learning HOW to get good code out of them? As with all things LLM there's a whole lot of undocumented and under appreciated depth to getting decent results. Code hallucinations are also the least damaging type of hallucinations, because you get fact checking for free: if you run the code and get an error you know there's a problem. A lot of the time I find pasting that error message back into the LLM gets…

> Code hallucinations are also the least damaging type of hallucinations, because you get fact checking for free: if you run the code and get an error you know there's a problem. This is great when the error is a thrown exception, but less great when the error is a subtle logic bug that only strikes in some subset of cases. For trivial code that only you will ever run this is probably not a big deal—you'll just fix i…

When they spit out these subtle bugs, are you promoting the LLM to watch our for that particular bug? I wonder if it just needs a vir more guidance in more explicit terms

Re: Things we learned about LLMs in 2024

#130
post #21
post #12

Earlier quoted context omitted.

If they are subsidised they can make a profit while still not making enough money to cover energy costs.

The tip I got about both Gemini and Nova is that the low prices they are charging still cover their energy costs.

OK!
Post reply on HN