News for hackers. Stuff that matters.
Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @02:33PM (#42561151)
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 LLMs is that their ability to help, as a tool, changes vastly based on your communication ability. The prompt is the king to make those models 10x better than they are with the lazy one-liner question. Drop your files in the context window; ask very precise questions explaining the background. They work great to explore what is at the borders of your knowledge. They are also great at doing boring tasks for which you can provide perfect guidance (but that still would take you hours). The best LLMs (in my case just Claude Sonnet 3.5, I must admit) out there are able to accelerate you.

Re:Things we learned about LLMs in 2024 by duped on Tuesday December 31, 2024 @04:18PM (#42561890)
> Try Claude Sonnet 3.5 (not Haiku!) and tell me if, while still flawed, is not helpful.

It's not as helpful as Google was ten years ago. It's more helpful than Google today, because Google search has slowly been corrupted by garbage SEO and other LLM spam, including their own suggestions.

Re:Things we learned about LLMs in 2024 by ChicagoDave on Tuesday December 31, 2024 @04:47PM (#42562105)
Claude Sonnet 3.5 can write whole React applications with proper contextual clues and some minor iterations. Google has never coded for you.

I’ve written two large applications and about a dozen smaller ones using Claude as an assistant.

I’m a terrible front-end developer and almost none of that work was possible without Claude. The API and AWS deployment were sped up tremendously.

I’ve created unit tests and I’ve read through the resulting code and it’s very clean. One of my core pre-prompt requirements has always been to follow domain-driven design principles, something a novice would never understand.

I also start with design principles and a checklist that Claude is excellent at providing.

My only complaint is you only have a 3-4 hour window before you’re cutoff for a few hours.

And needing an enterprise agreement to have a walled garden for proprietary purposes.

I was not a fan in Q1. Q2 improved. Q3 was a massive leap forward.

Re:Things we learned about LLMs in 2024 by duped on Tuesday December 31, 2024 @05:23PM (#42562296)
I've never really used Claude for writing code, becuase I'm not really bottlenecked by that problem. I have used it quite a bit for asking questions about what code to write and it's almost always wrong (usually in subtle ways that would trick someone with little experience).

Maybe it was overtrained on react sources, but for me it's pretty useless.

The big annoyance for me is it just makes up APIs that don't exist. While that's useful for suggesting to me what APIs I should add to my own code, it's really pointless if I ask a question like "using libfoo how do I bar" and it tells me "call the doBar() function" which does not exist.

Re:Things we learned about LLMs in 2024 by numpad0 on Tuesday December 31, 2024 @06:32PM (#42562661)
They can't think at all. The task must be strict macroexpansion of original input(doesn't mean that always works).

I'm suspecting LLM works for a lot of front end and app coding just because code in those fields are insanely overbloated and value proposition is almost disconnected from logic. There must be metric tons of typing in those fields, and in those areas LLMs must be useful. They certainly handle paper test questions well.

Re:Things we learned about LLMs in 2024 by csomar on Wednesday January 01, 2025 @02:31AM (#42564548)
They are mostly useful for front-end/React because front-end shouldn't been code in the first place. They can do the UX but not the state management. Honestly, as someone who sucks and dread UX building (and having to frequently adjust my divs/components), they are a life saver when you are doing very conventional things. That is things you can find 100s of examples of but will take you hours to glue together.
Re:Things we learned about LLMs in 2024 by deadbabe on Tuesday December 31, 2024 @06:41PM (#42562704)
Imagine not needing Claude to do any of that.
Re:Things we learned about LLMs in 2024 by ChicagoDave on Tuesday December 31, 2024 @07:21PM (#42562919)
This is one of those things I like about Claude.

I’m hitting my 40th year as a professional software developer and architect. I’ve written thousands of blocks of code from scratch. It gets boring.

But then in the 2000’s me (and everyone else) started building code generators, often from ERD structures, but also UML designs.

These tools were massively useful and (initially) reduced costs. The future balls of mud problems took over ten years to arrive.

But code generation has always been considered a smart and cost-effective approach to building software.

GenAI has “issues” and those have been exposed. One of my recent revelations is that Claude is best at TypeScript and python. C# (my home turf) is much lower in its skills capacity.

So in the last two months I’ve been building my apps in TypeScript instead of C# and have dramatically increased my productivity.

Claude will definitely fail if it doesn’t have the correct information. A good example is writing Bluesky apps. The docs are a mess and contradictory. But there are up to date docs on GitHub and if you include those in your project with instructions to only use those references, Claude’s hallucinations can be eliminated.

I don’t think AGI is a real possibility in my lifetime, and I do fear the future of software development when no one has actual coding experience, but for us boomers, it’s pretty darn useful.

Re:Things we learned about LLMs in 2024 by deadbabe on Tuesday December 31, 2024 @07:41PM (#42563012)
How are you measuring your productivity?
Re:Things we learned about LLMs in 2024 by ChicagoDave on Tuesday December 31, 2024 @08:30PM (#42563243)
In many cases I have no frame of reference for the expected code, like React and css. Typescript is perfectly readable, but I’m not really a script kiddie, so I’d go very slow on the React tsx files. The services are probably a slightly faster set of work, especially if I always have unit tests.

If someone was an expert React+TypeScript programmer with decent css knowledge the productivity may be a marginal improvement.

But I haven’t been a full-time programmer in ten years.

Re:Things we learned about LLMs in 2024 by emptiestplace on Tuesday December 31, 2024 @05:03PM (#42562205)
What a hilariously absurd statement. You might want to actually try it.
Re:Things we learned about LLMs in 2024 by bdangubic on Tuesday December 31, 2024 @04:52PM (#42562139)
comparing google to claude 3.5 is like comparing tesla s plaid with a horse
Re:Things we learned about LLMs in 2024 by jimt1234 on Wednesday January 01, 2025 @09:14PM (#42571017)
Google Search has been corrupted by...Google.
Re:Things we learned about LLMs in 2024 by qsort on Tuesday December 31, 2024 @04:17PM (#42561887)
I believe it's more frustration directed at the mismatch between marketing and reality, combined with the general well deserved growing hatred for SV culture, and, more broadly, software engineers. The sentiment would be completely different if the entire industry marketed themselves like the helpful tools they are rather than the second coming of Christ they aren't. This distinction is hard to make on "fast food" forums like this one.

If you aren't a coder, it's hard to find much utility in "Google, but it burns a tree whenever you make an API call, and everything it tells you might be wrong". I for one have never used it for anything else. It just hasn't ever come up.

It's great at cheating on homework, kids love GPTs. It's great at cheating in general, in interviews for instance. Or at ruining Christmas, after this year's LLM debacle it's unclear if we'll have another edition of Advent of Code. None of this is the technology's fault, of course, you could say the same about the Internet, phones or what have you, but it's hardly a point in favor either.

And if you are a coder, models like Claude actually do help you, but you have to monitor their output and thoroughly test whatever comes out of them, a far cry from the promises of complete automation and insane productivity gains.

If you are only a consumer of this technology, like the vast majority of us here, there isn't that much of an upside in being an early adopter. I'll sit and wait, slowly integrating new technology in my workflow if and when it makes sense to do so.

Happy new year, I guess.

Re:Things we learned about LLMs in 2024 by fragmede on Tuesday December 31, 2024 @08:44PM (#42563307)
> there isn't that much of an upside in being an early adopter.

Other than, y'know, using the new tools. As a programmer heavy forum, we focus a lot on LLMs' (lack of) correctness. There's more than a little bit of annoyance when things are wrong, like being asked to grab the red blanket and then getting into an argument over it being orange instead of what was important, someone needed the blanket because they were cold.

Most of the non-tech people who use ChatGPT that I've talked to absolutely love it because they don't feel it judges them for asking stupid questions and they have conversations about absolutely everything in their lives with it down to which outfit to wear to the party. There are wrong answers to that question as well, but they're far more subjective and just having another opinion in the room is invaluable. It's just a computer and won't get hurt if you totally ignore it's recommendations, and even better, it won't gloat (unless you ask it to) if you tell it later that it was right and you were wrong.

Some people have found upsides for themselves in their lives, even at this nascent stage. No one's forcing you to use one, but your job isn't going to be taken by AI, it's going to be taken by someone else who can outperform you that's using AI.

Re:Things we learned about LLMs in 2024 by saltcured on Tuesday December 31, 2024 @10:24PM (#42563714)
Yikes.

Clearly said, yet the general sentiment awakens in me a feeling more gothic horror than bright futurism. I am stuck with wonder and worry at the question of how rapidly this stuff will infiltrate into the global tech supply chain, and the eventual consequences of misguided trust.

To my eye, too much current AI and related tech are just exaggerated versions of magic 8-balls, Ouija boards, horoscopes, or Weizenbaum's ELIZA. The fundamental problem is people personifying these toys and letting their guard down. Human instincts take over and people effectively social engineer themselves, putting trust in plausible fictions.

It's not just LLMs though. It's been a long time coming, the way modern tech platforms have been exaggerating their capability with smoke and mirrors UX tricks, where a gleaming facade promises more reality and truth than it actually delivers. Individual users and user populations are left to soak up the errors and omissions and convince themselves everything is working as it should.

Someday, maybe, anthropologists will look back on us and recognize something like cargo cults. When we kept going through the motions of Search and Retrieval even though real information was no longer coming in for a landing.

Re:Things we learned about LLMs in 2024 by uludag on Tuesday December 31, 2024 @03:18PM (#42561504)
I don't think people finding LLMs useless is a good representation of the general sentiment though. I feel that more than anything, people are annoyed at LLM slop. Someone uses an LLM too much to write code, they create "slop," which ends up making things worse.
Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @04:03PM (#42561815)
Unfortunately complex tools will be misused by part of the population. There is no easy escape from that in the modernity of possibilities. Look at the Internet itself.
Re:Things we learned about LLMs in 2024 by gre on Tuesday December 31, 2024 @03:35PM (#42561632)
Yes but then they can prompt it to golf the code and most of the slop goes away. This sometimes breaks the code.
Re:Things we learned about LLMs in 2024 by ninth_ant on Tuesday December 31, 2024 @02:59PM (#42561349)
I think a lot of the confusion is in how we approach LLMs. Perhaps stemming from the over-broad term “AI”.

There are certain classes of problems that LLMs are good at. Accurately regurgitating all accumulated world knowledge ever is not one, so don’t ask a language model to diagnose your medical condition or choose a political candidate.

But do ask them to perform suitable tasks for a language model! Every day by automation I feed in the hourly weather forecast my home ollama server and it builds me a nice readable concise weather report. It’s super cool!

There are lots of cases like this where you can give an LLM reliable data and ask it to do a language related task and it will do an excellent job of it.

If nothing else it’s an extremely useful computer-human interface.

Re:Things we learned about LLMs in 2024 by rrix2 on Tuesday December 31, 2024 @03:09PM (#42561420)
> Every day by automation I feed in the hourly weather forecast my home ollama server and it builds me a nice readable concise weather report.

not to dissuade you from a thing you find useful but are you aware that the national weather service produces an Area Forecast Discussion product in each local NWS office daily or more often that accomplishes this with human meteorologists and clickable jargon glossary?

https://forecast.weather.gov/product.php?site=SEW&issuedby=S...

Re:Things we learned about LLMs in 2024 by ninth_ant on Tuesday December 31, 2024 @05:17PM (#42562266)
Doesn’t dissuade me at all, that’s a really neat service. I’m not American though, and even if my own country had a similar service I still enjoying tuning the results to focus on what I’m interested in. And it was just an example of the kinds of computer-human interfaces that are newly possible from this technology.

Anytime you have data and want it explained in a casual way — and it’s not mission critical to be extremely precise — LLMs are going to be a good option to consider.

More useful AGI-like behaviours may be enabled by combining LLMs with other technologies down the line, but we shouldn’t try to pretend that LLMs can do everything nor are they useless.

Re:Things we learned about LLMs in 2024 by LtWorf on Wednesday January 01, 2025 @02:42AM (#42564571)
The best forecast available on the internet is norwegian.
Re:Things we learned about LLMs in 2024 by pixl97 on Tuesday December 31, 2024 @05:12PM (#42562236)
>don’t ask a language model to diagnose your medical condition

Honestly they are very decent at it if you give them accurate information in which to make the diagnosis. The typical problem people have is being unable to feed accurate information to the model. They'll cut out parts they don't want to think about or not put full test results in for consideration.

Re:Things we learned about LLMs in 2024 by LtWorf on Wednesday January 01, 2025 @02:43AM (#42564576)
Yes so basically bias it into what you think it should reply in the question and it will magically somehow give the reply you wanted! Very useful :D
Re:Things we learned about LLMs in 2024 by ninth_ant on Wednesday January 01, 2025 @12:51PM (#42567679)
If the LLM is trained on accurate medical data and you provide accurate symptoms data, then the LLM can be a useful tool to output the information in a human-readable way.

This is not a diagnosis. Any reasonably capable person can read webmd and apply the symptoms listed and compare them to what the patient describes. This is widely regarded as dangerous because the input data as well as the patient data are limited in ways that can be medically relevant.

So even if you can use it as a good substitute for browsing webmd, it’s still not a substitute for seeing a medical professional. And for the foreseeable future it will not be.

Re:Things we learned about LLMs in 2024 by capr on Monday January 06, 2025 @06:07AM (#42609584)
compared to what? most doctors never heard of Bayes rule
Re:Things we learned about LLMs in 2024 by sdesol on Tuesday December 31, 2024 @06:59PM (#42562813)
> Perhaps stemming from the over-broad term “AI”.

No, I think if we follow the money, we will find the problem.

Re:Things we learned about LLMs in 2024 by dinosaurdynasty on Tuesday December 31, 2024 @07:01PM (#42562827)
> choose a political candidate

I actually found 4o+search to be really good at this... Admittedly what I did was more "research these candidates, tell me anything newsworthy, pros/cons, etc" (much longer prompt) and well, it was way faster/patient at finding sources than I ever would've been, telling me things I never would've figured out with <5 minutes of googling each set of candidates (which is what I've done before).

Honestly my big rule for what LLMs are good at is stuff like "hard/tedious/annoying to do, easy to verify" and maybe a little more than that. (I think after using a model for a while you can get a "feel" for when it's likely BSing.)

Re:Things we learned about LLMs in 2024 by pella on Tuesday December 31, 2024 @07:20PM (#42562912)
> so don’t ask a language model to diagnose your medical condition

(o1-preview) LLMs show promise in clinical reasoning but fall short in probabilistic tasks, underscoring why AI shouldn't replace doctors for diagnosis just yet.

"Superhuman performance of a large language model on the reasoning tasks of a physician" https://arxiv.org/abs/2412.10849 [14 Dec 2024]

Re:Things we learned about LLMs in 2024 by mvdtnz on Tuesday December 31, 2024 @10:03PM (#42563626)
> Every day by automation I feed in the hourly weather forecast my home ollama server and it builds me a nice readable concise weather report. It’s super cool!

You feed it a weather report and it responds with a weather report? How is that useful?

Re:Things we learned about LLMs in 2024 by hansvm on Wednesday January 01, 2025 @12:41AM (#42564202)
It distilled bulk information into a form the author cared about. If nothing else it was probably fun, and a personal report on the things you care about can save minutes each day.

I did something similar awhile back without LLMs. I enjoy kayaking, but for a variety of reasons [0] it's usually unwieldy to break out of the surf and actually get out into the ocean at my local beach. I eventually started feeding the data into an old-school ML model where I'd manually check the ocean and report on a few factors (breaking waves, unsafe wind magnitude/direction, ...). The model converted those weather/tide reports into signals I cared about, and then my forecast could simply AND all those together and plot them on a calendar.

An LLM is less custom in some sense, but if you have certain routines you care about (e.g., commuting to my last job I'd always avoid the 101 in favor of 280 if there was heavy rain), it's easy to let the computer translate raw weather information into signals you care about (should you take an alternate route, should you alter your schedule, ...).

Off-topic, do you know of a good source of weather covariates? E.g., a report with a 50% chance of rain for 2hr can easily mean light rain guaranteed for 2hr, a guaranteed 1hr of rain sometime in that 2hr period, a 50% chance that a 2hr storm will hit your town or the next town over, or all kinds of things. Does anybody report those raw model outputs?

[0] There isn't any protection from the open ocean (combined with a kayak that's a bit too top-heavy for the task at hand), which doesn't help, but the big problem is a sand bar just off the coast. If the tide isn't just right, even small swells are amplified into large breaking waves, and I don't particularly mind getting dumped upside down onto a sand bar, but I'd really prefer to spend that time in slightly calmer waters.

Re:Things we learned about LLMs in 2024 by ninth_ant on Wednesday January 01, 2025 @01:01PM (#42567757)
Well said, that’s exactly what I meant.
Re:Things we learned about LLMs in 2024 by minimaxir on Tuesday December 31, 2024 @02:54PM (#42561315)
> Claude Sonnet 3.5 (not Haiku!)

A very big surprise is just how much better Sonnet 3.5 is than Haiku. Even the confusingly-more-expensive-Haiku-variant Haiku 3.5 that's more recent than Sonnet 3.5 is still much worse.

Re:Things we learned about LLMs in 2024 by jsheard on Tuesday December 31, 2024 @03:30PM (#42561597)
I swear these goalposts keep getting moved, I remember being told that GPT3.5 is a useless toy but the paid GPT4 is lifechanging, and now that GPT4 is free I'm told that it's a useless toy but paid o1 or paid Sonnet are lifechanging. Looking forward to o1 and Sonnet becoming useless toys, unlike the lifechanging o3.
Re:Things we learned about LLMs in 2024 by aetherson on Tuesday December 31, 2024 @03:47PM (#42561712)
You will also be dismayed to hear that a 2011 iPhone is no longer state-of-the-art, and indeed can't run most modern apps.
Re:Things we learned about LLMs in 2024 by jpc0 on Tuesday December 31, 2024 @04:22PM (#42561914)
GPT4 is a 13 year old technology? Compared to o1 and Sonnet 3.5?

If someone told me an iPhone 4 is terrible but an iPhone 5 would definitely serve my needs, then when I get an iPhone 5 they say the same of the 6 you really want me to believe them a second time? Then a third time? Then a 4th? In the mean time my time and money is wasted?

Re:Things we learned about LLMs in 2024 by scubbo on Tuesday December 31, 2024 @04:23PM (#42561925)
Holy false-equivalency, Batman! The definitions of "useless toy / lifechanging tool" are _not_ changing over time (or, at least, not over the timescale being explored here), whereas the expectations and requirements of processing power of a phone are.
Re:Things we learned about LLMs in 2024 by aetherson on Wednesday January 01, 2025 @11:52AM (#42567205)
But in fact they are changing over time -- this is an expectations treadmill. When you get something newer and better, it highlights the flaws in what you had before.
Re:Things we learned about LLMs in 2024 by scubbo on Wednesday January 01, 2025 @06:04PM (#42570044)
That is true _in general_, but not in this specific case (hence why I specified "not over the timescale being explored here"). A modern cigarette-lighter would indeed have been a life-changing tool to a caveman but is indeed disposable junk today.

The point being made by the original comment (with which I agree) was that many criteria-for-usefulness - primarily that of reliability or a lack of hallucination - have remained static; with successive generations of tools being (falsely) claimed to meet them, but then abandoned when the next hype-train comes along.

I certainly agree that _some_ aspects of AI models are indeed improving (often drastically!) over time (speed, price, supported formats, history/context, etc.) - but they still _all_ fall _drastically_ short on the key core requirement that is required in order to make them Actually Useful. "X is better than Y" does not imply "where Y failed to be useful, X now succeeds".

Re:Things we learned about LLMs in 2024 by johnrob on Tuesday December 31, 2024 @06:35PM (#42562677)
It would be quite useful if that were the only phone available.
Re:Things we learned about LLMs in 2024 by raincole on Tuesday December 31, 2024 @10:14PM (#42563671)
Except GPT4 isn't free.

The GP is claiming GPT4o is bad but Sonnet is good. GPT4o is about only 20% cheaper than Sonnet.

Re:Things we learned about LLMs in 2024 by mhh__ on Tuesday December 31, 2024 @02:55PM (#42561316)
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.
Re:Things we learned about LLMs in 2024 by minimaxir on Tuesday December 31, 2024 @02:55PM (#42561320)
Brand awareness is a hell of a drug.
Re:Things we learned about LLMs in 2024 by mhh__ on Tuesday December 31, 2024 @03:12PM (#42561453)
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 by dxbydt on Tuesday December 31, 2024 @02:57PM (#42561331)
> best LLMs are able to accelerate you

https://www2.math.upenn.edu/~ghrist/preprints/LAEF.pdf - this math textbook was written in just 55 days!

Paraphrasing the acknowledgements -

...Begun November 4, 2024, published December 28, 2024.

...assisted by Claude 3.5 sonnet, trained on my previous books...

...puzzles co-created by the author and Claude

...GPT-4o and -o1 were useful in latex configurations...doing proof-reading.

...Gemini Experimental 1206 was an especially good proof-reader

...Exercises were generated with the help of Claude and may have errors.

...project was impossible without the creative labors of Claude

The obvious comparison is to the classic Strang https://math.mit.edu/~gs/everyone/ which took several *years* to conceptualize, write, peer review, revise and publish.

Ok maybe Strang isn't your cup of tea, :%s/Strang/Halmos/g , :%s/Strang/Lipschutz/g, :%s/Strang/Hefferon/g, :%s/Strang/Larson/g ...

Working through the exercises in this new LLMbook, I'm thinking...maybe this isn't going to stand the test of time. Maybe acceleration is not so hot after all.

Re:Things we learned about LLMs in 2024 by pton_xd on Tuesday December 31, 2024 @03:15PM (#42561472)
"The story of linear algebra begins with systems of equations, each line describing a constraint or boundary traced upon abstract space. These simplest mathematical models of limitation — each equation binding variables in measured proportion — conjoin to shape the realm of possible solutions. When several such constraints act in concert, their collaboration yields three possible fates: no solution survives their collective force; exactly one point satisfies all bounds; or infinite possibilities trace curves and planes through the space of satisfaction. This trichotomy — of emptiness, uniqueness, and infinity — echoes through all of linear algebra, appearing in increasingly sophisticated forms as our understanding deepens."

Maybe I'm not the target audience, but... that really doesn't make me interested in continuing to read.

Re:Things we learned about LLMs in 2024 by jpc0 on Tuesday December 31, 2024 @04:24PM (#42561935)
Even putting it here is annoying to me... Those are a lot of words saying nothing that I just spend time reading.

I'm agreeing with you.

Re:Things we learned about LLMs in 2024 by wrs on Tuesday December 31, 2024 @06:09PM (#42562557)
It's rather purple prose, but it's entirely meaningful. Maybe it doesn't seem to mean anything until after you know some linear algebra, though...
Re:Things we learned about LLMs in 2024 by dxbydt on Tuesday December 31, 2024 @08:44PM (#42563304)
its been a long time, but when i was taught this material, i was told there are only 3 cases -

x+y=1, x+y=2 clearly has no solution since two numbers can’t simultaneously add to both one and two.

x+y=1,2x+2y=2 clearly has infinitely many solutions. There’s only one equation here after canceling the 2, so you can plug in x’s and y’s all day long, no end to it.

x+y=1, 2x+y=1 clearly has exactly one solution (0,1) after elimination.

This example stuck with me so I use it even now. The author/Claude/Gemini/whatever could have just used this simple example instead of “trichotomy of curves through space conjoin through the realm of …” math, not Shakespeare.

Re:Things we learned about LLMs in 2024 by wrs on Tuesday December 31, 2024 @10:48PM (#42563826)
Sure, but saying something in an ornate way is not the same as “saying nothing”.
Re:Things we learned about LLMs in 2024 by BlueTemplar on Wednesday January 01, 2025 @08:12AM (#42565812)
Also, isn't this a great example of "when you have a hammer, everything looks like a nail" ?

To explain this I would first and foremost use a picture, where the 3 cases : parallel, identical, intersection can be intuitively seen (using our visual system, rather than our language system), with merely a glance.

Re:Things we learned about LLMs in 2024 by sureglymop on Tuesday December 31, 2024 @06:08PM (#42562552)
I agree. Not what I would expect from a math book or script.
Re:Things we learned about LLMs in 2024 by jcranmer on Wednesday January 01, 2025 @12:26AM (#42564157)
That is such supremely bad writing that it can only come from AI being told to spice up the original opening paragraph, and short of the original author being barely literate (and possibly even then), the original text would have been better writing.

The overuse of the $15 synonyms is almost always a bad idea--you want to use them sparingly, where dropping them in for their subtly different meanings enhances the text. But what is extremely sloppy here is that the possibilities of "no solutions, one solution, infinite solutions" is now being described with a different metaphor for solution here. And by the end of the paragraph, I'm not actually sure what point I'm supposed to take away from this text. (As bad as this paragraph is, the next paragraph is actually far worse.)

Mathematics already has a problem for the general audience with a heavy focus on abstraction that can be difficult to intuit on more concrete objects. Adding florid metaphors to spice up your writing makes that problem worse.

Re:Things we learned about LLMs in 2024 by kianN on Tuesday December 31, 2024 @03:05PM (#42561391)
^ This perfectly encapsulates the story I see every time someone digs into the details of any llm generated or assisted content that has any level of complexity.

Great on the surface but lacks any depth, cohesive, or substance

Re:Things we learned about LLMs in 2024 by datadrivenangel on Tuesday December 31, 2024 @03:01PM (#42561365)
Going faster isn't good if the quality drops enough that overall productivity decreases... Infinite slop is only a good thing for pigs.
Re:Things we learned about LLMs in 2024 by cruffle_duffle on Tuesday December 31, 2024 @03:58PM (#42561775)
Just use ChatGPT to summarize its own output. It’s like running your JPEG back through the JPEG compressor again!
Re:Things we learned about LLMs in 2024 by mooreds on Tuesday December 31, 2024 @03:43PM (#42561693)
I started a book about CIAM (customer identity and access management) using Claude to help outline a chapter. I'd edit and refine the outline to make sure it covered everything.

Then I'd have Claude create text. I'd then edit/refine each chapter's text.

Wow, was it unpleasant. It was kinda cool to see all the words put together, but editing the output was a slog.

It's bad enough editing your own writing, but for some reason this was even worse.

Re:Things we learned about LLMs in 2024 by dxbydt on Tuesday December 31, 2024 @08:29PM (#42563238)
just to clarify - I have nothing to do with this book. I was just forwarded a copy and I thought its relevant to the topic at hand. from the wild swings in karma, looks like people are annoyed with the message and shooting down the messenger.
Re:Things we learned about LLMs in 2024 by hdjjhhvvhga on Tuesday December 31, 2024 @02:40PM (#42561218)
While Claude Sonnet is superior than 4o for most my use cases, there are still occasionally some specific tasks where it performs slightly better.
Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @02:43PM (#42561249)
Probably. But statistically to work with 4o is a lose of time for me. LLMs is like an investment: you write the prompts, you "work" with them. If the LLM is too weak, this is a lose of time. You need to have a return on the investment that is positive. With ChatGPT 4o / o1 most of the times for me the investment of time has almost zero return. Before Claude Sonnet 3.5 I already had a ChatGPT PRO account but never used it for coding since it was most of the times useless if not for throw away scripts that I didn't want to do myself or as a stack overflow replacement for trivial stuff. Now it's different.
Re:Things we learned about LLMs in 2024 by airstrike on Tuesday December 31, 2024 @03:00PM (#42561357)
This mirrors my experience 100%. I'm not even sure why I still pay for OpenAI at this point. Claude 3.5 is just incredibly superior. And I totally agree on the point about dropping in context and asking very specific questions. I've had Claude pinpoint a bug in a 2k LOC module that I was struggling to find the cause for. After wasting a lot of time on it on my own, I thought "what the heck, maybe Claude can figure it out" and it did. It's objectively useful, even if flawed sometimes.
Re:Things we learned about LLMs in 2024 by hanikesn on Wednesday January 01, 2025 @01:57AM (#42564423)
I'm curious. Can you go into more detail what kind of bug it found?
Re:Things we learned about LLMs in 2024 by airstrike on Wednesday January 01, 2025 @12:41PM (#42567577)
I was writing a custom widget for iced (the Rust GUI library) and I was getting a panic due to some fancy logic I was trying to do. I guess the shortest description I can say is that it was a combination of what appeared to be a caching issue at first, but the real cause turned out to be some method shadowing where I was using a struct's method where I meant to use the trait's method.

I had made the specific operation generic (moving it out of the struct and into a trait) but forgot to delete it from the struct, so I was calling the incorrect function. Claude pinpointed the cache issue immediately when I just dumped two files into the context and asked it:

    somewhere in my codebase I'm triggering a perform() on the editor but the next call on highlight() panics because `Line layout should be cached`

    what am I missing? do I need to do something after perform() to re-cache the layout?
at first that seemed to fix the issue, but other errors persisted. so we kept debugging together until we found the root cause. either way I knew where to look thanks to its assistance
Re:Things we learned about LLMs in 2024 by d0mine on Tuesday December 31, 2024 @05:43PM (#42562404)
why "lose of time" instead of "loss of time" Is it a typo or fingerprinting?
Re:Things we learned about LLMs in 2024 by fragmede on Tuesday December 31, 2024 @08:46PM (#42563318)
it's "proof" that it wasn't written by an LLM (but let me delve into this issue).
Re:Things we learned about LLMs in 2024 by squirrel on Wednesday January 01, 2025 @01:29AM (#42564326)
Typo
Re:Things we learned about LLMs in 2024 by tootie on Tuesday December 31, 2024 @05:43PM (#42562403)
Like what? Claude has become my go-to, but I find that it's wrong enough often enough that I really can't trust it for anything. If it says something I have to go dig through it's citations very carefully.
Re:Things we learned about LLMs in 2024 by wslh on Tuesday December 31, 2024 @02:36PM (#42561175)
Right, in simpler terms: The measure of LLMs success is how effectively they help you achieve your goal faster.
Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @02:37PM (#42561192)
Exactly, and right now the LLMs acceleration effect is a tool, not "give me the final solution". Even people that can't code, using LLMs to build applications from scratch, still have this tool mindset. This is why they can use them effectively: they don't stop at the first failed solution; they provide hints to the LLM, test the code, try to figure what's the problem (also with the LLM help), and so forth. It's a matter of mindset.
Re:Things we learned about LLMs in 2024 by d0mine on Tuesday December 31, 2024 @05:59PM (#42562502)
btw, fusion has arrived by that definition: No reactors that would produce more energy than they consume, But net positive reactions have been achieved. Tasks where LLMs output is more than 1x are few and far between.
Re:Things we learned about LLMs in 2024 by andrewaylett on Wednesday January 01, 2025 @07:33AM (#42565648)
> people that can't code

These people may not be Software Engineers, but they are coding.

Re:Things we learned about LLMs in 2024 by cruffle_duffle on Tuesday December 31, 2024 @03:26PM (#42561573)
To get the most out of them you have to provide context. Treat these models like some kind of eager beaver junior engineer who wants to jump in and write code without asking questions. Force it to ask questions (eg: “do not write code yet, please restate my requirements to make sure we are in alignment. Are there any extra bits of context or information that would help? I will tell you when to write code”)

If your model / chat app has the ability to always inject some kind of pre-prompt make sure to add something like “please do not jump to writing code. If this was a coding interview and you jumped to writing code without asking questions and clarifying requirements you’d fail”.

At the top of all your source files include a comment with the file name and path. If you have a project on one of these services add an artifact that is the directory tree (“tree —-gitignore” is my goto). This helps “unaided” chats get a sense of what documents they are looking at.

And also, it’s a professional bullshitter so don’t trust it with large scale code changes that rely on some language / library feature you don’t have personal experience with. It can send you down a path where the entire assumption that something was possible turns out to be false.

Does it seek like a lot of work? Yes. Am I actually more productive with the tool than without? Probably. But it sure as shit isn’t “free” in terms of time spent providing context. I think the more I use these models, the more I get a sense of what it is good at and what is going to be a waste of time.

Long story short, prompting is everything. These things aren’t mind readers (and worse they forget everything in each new session)

Re:Things we learned about LLMs in 2024 by layer8 on Tuesday December 31, 2024 @06:34PM (#42562669)
You are right, but doing all that is incredibly cumbersome, at least to some people, which is why they don’t like working with LLMs.
Re:Things we learned about LLMs in 2024 by simonw on Tuesday December 31, 2024 @06:36PM (#42562681)
That was one of the themes of my article: LLMs are power-user tools, mis-sold as "easy to use". To get great results out of them you need to invest a whole lot of under-documented and under-appreciated effort. https://simonwillison.net/2024/Dec/31/llms-in-2024/#llms-som...
Re:Things we learned about LLMs in 2024 by layer8 on Tuesday December 31, 2024 @07:26PM (#42562941)
It’s not just that you need to be a power user (I certainly am), you also need to be fine with nondeterminism and typing a lot of prose, instead of doing everything with keyboard shortcuts and CLI commands, with reproducible outcomes. It’s a different mode of operation and interaction, requiring a different predisposition to some degree.
Re:Things we learned about LLMs in 2024 by fragmede on Tuesday December 31, 2024 @08:52PM (#42563355)
unless you can type faster than you can talk, (which some people can), stop typing and start dictating. aider has a /voice command for a reason.

I don't use it exclusively, but damn does it help in the right places.

Re:Things we learned about LLMs in 2024 by eterps on Wednesday January 01, 2025 @06:14AM (#42565355)
Can you elaborate, or give some examples? I am having trouble imagining in which situations that would be useful because I tend to put a lot of thought into defining the right prompt before sending it over.
Re:Things we learned about LLMs in 2024 by madmask on Wednesday January 01, 2025 @02:56AM (#42564624)
Exactly! I don’t like talking or writing or explaining.

My mind generally uses language as little as possible, I have no inner monologue running in the background.

Greatly prefer something deterministic to random bs popping up without the ability of recognizing it.

I don’t like llms but sometimes use them as autocomplete or to generate words, like a template for a letter or boilerplate scripts, never for actual information (à la google).

Re:Things we learned about LLMs in 2024 by 1oooqooq on Tuesday December 31, 2024 @03:12PM (#42561448)
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 by brookst on Tuesday December 31, 2024 @02:49PM (#42561293)
I’m surprised you only have one use case. I use LLMs to research travel, adjust recipes, check biographies and book reviews, and many many more things.
Re:Things we learned about LLMs in 2024 by swalsh on Tuesday December 31, 2024 @04:46PM (#42562099)
I'm a big believer in Claude. I've accomplished some huge productivity gains by leveraging it. That said, I can see places where the models are strong and weak. If you're doing react, or python. These models are incredible. C#, C++ they're not terrible. Rust though, it's not great. If your experience is exclusively trying to use it to write Rust, it doesn't matter if you're using o1, Claude or anything else. It's just not great at it yet.
Re:Things we learned about LLMs in 2024 by mvkel on Tuesday December 31, 2024 @04:48PM (#42562111)
I'm surprised at the description that it's "useless" as a programming / design partner. Even if it doesn't make "elegant" code (whatever that means), it's the difference between an app existing at all, or not.

I built and shipped a Swift app to the App Store, currently generating $10,200 in MRR, exclusively using LLMs.

I wouldn't describe myself as a programmer, and didn't plan to ever build an app, mostly because in the attempts I made, I'd get stuck and couldn't google my way out.

LLMs are the great un-stickers. For that reason per se, they are incredibly useful.

Re:Things we learned about LLMs in 2024 by theptip on Tuesday December 31, 2024 @06:06PM (#42562541)
The context here is super-important - the commenter is the author of Redis. So, a super-experienced and productive low-level programmer. It’s not surprising that Staff-plus experts find LLMs much less useful.

Though I’d be interested if this was an opinion on “help me write this gnarly C algorithm” or “help me to be productive in <new language>” as I find a big productivity increase from the latter.

Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @07:27PM (#42562943)
Quick example. I was implementing dot product between two quantized vectors that have two different min/max quantization ranges (later I changed the implementation to just centered range quantization, thanks to Claude and what I'm writing in this comment). I wanted to still have the math with the integers and adjust for the ranges at the end. Claude was able to mathematically scompose the operations as multiplication and accumulation of a sum of integers and later adjust the result, using a math trick that I didn't know but was understandable after having seen it. This way I was able to benchmark this implementation understanding that my old centered quantization was not less precise in practice and faster (I can multiply integers without taking the sum, and later fix for the square of the range factor). I'd do it without LLMs but probably I would not try at all because of the time needed.

Other examples: Claude was able multiple times to spot bugs in my C code, when I asked for a code review. All bugs I would eventually find but that it's better to fix ASAP.

Finally sometimes I put relevant papers and implementations and ask for variations of a given algoritm among the paper and the implementations around, to gain insights about what people do in the practice. Then engage in discussions about how to improve it. It is never able to come up with novel ideas but is able to recognize often times when my idea is flawed or if it seems sounding.

All this and more helps me to deliver better code. I can venture in things I otherwise would not do for lack of time.

Re:Things we learned about LLMs in 2024 by YeGoblynQueenne on Tuesday December 31, 2024 @09:11PM (#42563449)
>> scompose the operations

I wonder whether that is some specialised terminology I'm not familiar with - or it just means to decompose the operations (but with an Italian s- for negation)?

Re:Things we learned about LLMs in 2024 by antirez on Tuesday December 31, 2024 @09:36PM (#42563527)
Decompose indeed :)
Re:Things we learned about LLMs in 2024 by beoberha on Wednesday January 01, 2025 @01:35AM (#42564353)
LLMs being able to detect bugs in my own code is absolutely mind blowing to me. These things are “just” predicting the next token, but somehow are able to take in code that has never been written before and somehow understand it and find what’s wrong with it.

I think I’m more amazed by them because I know how they work. They shouldn’t be able to do this, but the fact that they can is absolutely jaw dropping science fiction shit.

Re:Things we learned about LLMs in 2024 by nashadelic on Wednesday January 01, 2025 @04:00AM (#42564855)
I actually get annoyed when experienced folks say this isn't AGI, its next word predict and not human-like intelligence. But we don't know how human intelligence works. Is it also just a matrix of neuron weights? Maybe it ends up looking like humans are also just next-word/thought predictors. Maybe that is what AGI will be.
Re:Things we learned about LLMs in 2024 by miki123211 on Wednesday January 01, 2025 @06:04AM (#42565325)
A good enough next-word predictor IS AGI.

If there's something that you can prompt with e.g. "here's the proof for Fermat's last theorem" or "here is how you crack Satoshi's private key on a laptop in under an hour" and get a useful response, that's AGI.

Just to be clear, we are nowhere near that point with our current LLMs, and it's possible that we'll never get there, but in principle, if such a thing existed, it would be a next-word predictor while still being AGI.

Re:Things we learned about LLMs in 2024 by mewpmewp2 on Wednesday January 01, 2025 @07:00AM (#42565522)
This by the common definition isn't AGI yet, not to say it couldn't be. But if it was AGI it would be extremely clear, since it would also be able to control the physical form of itself. It needs robotics and to be able to navigate the world to be able to be AGI.
Re:Things we learned about LLMs in 2024 by latexr on Wednesday January 01, 2025 @07:24AM (#42565622)
> I actually get annoyed when experienced folks say this isn't AGI, its next word predict and not human-like intelligence. But we don't know how human intelligence works.

I’m pretty sure you’re committing a logical fallacy there. Like someone in antiquity claiming “I get annoyed when experienced folks say thunderstorms aren’t the gods getting angry, it’s nature and physical phenomena. But we don’t know how the weather works”. Your lack of understanding in one area does not give you the authority to make a claim in another.

Re:Things we learned about LLMs in 2024 by deterministic on Friday January 03, 2025 @03:02AM (#42583608)
A human can learn from just a few examples of chairs what a chair is. Machine learning requires way more training than that. So there does seem to be a difference in how human intelligence works.
Re:Things we learned about LLMs in 2024 by inciampati on Wednesday January 01, 2025 @03:48AM (#42564801)
> They shouldn't be able to do this

Really? ;) I guess you don't believe in the universal approximation theorem?

UAT makes a strong case that by reading all of our text (aka computational traces) the models have learned a human "state transition function" that understands context and can integrate within it to guess the next token. Basically, by transfer learning from us they have learned to behave like universal reasoners.

Re:Things we learned about LLMs in 2024 by zmgsabst on Wednesday January 01, 2025 @03:06AM (#42564656)
Why shouldn’t they be able to do this?

DNNs implicitly learn a type theory, which they then reason in. Even though the code itself is new, it’s expressible in the learned theory — so the DNN can operate on it.

Re:Things we learned about LLMs in 2024 by Jensson on Wednesday January 01, 2025 @04:56AM (#42565052)
Its easy to see how it does that, the answer is that your bug isn't something novel, it has seen millions of "where is the bug in this code" questions online so it can typically guess from there what it would be.

It is very unreliable at fixing things or writing code for anything non standard. Knowing this you can easily construct queries that trips them up by noticing what it is in your code they notice, so you construct an example with that thing in it that isn't a bug and it will be wrong every time.

Re:Things we learned about LLMs in 2024 by scrollaway on Wednesday January 01, 2025 @07:56AM (#42565743)
Both of your claims are way off the mark (I run an AI lab).

The LLMs are good at finding bugs in code not because they’ve been trained on questions that ask for existing bugs, but because they have built a world model in order to complete text more accurately. In this model, programming exists and has rules and the world model has learned that.

Which means that anything nonstandard … will be supported. It is trivial to showcase this: just base64 encode your prompts and see how the LLMs respond. It’s a good test because base64 is easy for LLMs to understand but still severely degrades the quality of reasoning and answers.

Re:Things we learned about LLMs in 2024 by Jensson on Wednesday January 01, 2025 @08:25AM (#42565876)
> just base64 encode your prompts and see how the LLMs respond

This is done via translations, LLM are good at translations, being able to translate doesn't mean you understand the subject.

And no I am not wrong here, I've tested this before, for example if you ask if a CPU model is faster than a GPU model it will say the GPU model is faster, even if the CPU is much more modern and faster overall since it learned that GPU names are faster than CPU names it didn't really understood what faster meant there. Exactly what the LLM gets wrong depends on the LLM of course, and the larger it is the more fine grained these things are but in general it doesn't really have much that can be called understanding.

If you don't understand how to break the LLM like this then you don't really understand what the LLM is capable of, so it is something everyone who uses LLM should know.

Re:Things we learned about LLMs in 2024 by scrollaway on Wednesday January 01, 2025 @07:35PM (#42570537)
That doesn't mean anything. Asking "which is faster" is fact retrieval, which LLMs are bad at unless they've been trained on those specific facts. This is why hallucinations are so prevalent: LLMs learn rules better than they learn facts.

Regardless of how the base64 processing is done (which is really not something you can speculate much on, unless you've specifically researched it -- have you?), my point is that it does degrade the output significantly while still processing things within a reasonable model of the world. Doing this is a rather reliable way of detaching the ability to speak from the ability to reason.

Re:Things we learned about LLMs in 2024 by Jerrrry on Wednesday January 01, 2025 @08:07PM (#42570708)
Asking characteristics about the result cause performance to drop because it's essentially asking the model to model itself implicitly/explicitly.

Also the more "factoids" / clauses needed to answer accurately are inversely proportional to the "correctness" of the final answer (on average, when prompt-fuzzed).

This is all because the more complicated/entropic the prompt/expected answer, the less total/accumulative attention has been spent on it.

  >What is the second character of the result of the prompt "What is the name of the president of the U.S. during the most fatal terror attack on U.S. soil?"
Re:Things we learned about LLMs in 2024 by HarHarVeryFunny on Wednesday January 01, 2025 @10:19AM (#42566511)
The "world model" of an LLM is just the set of [deep] predictive patterns that it was induced to learn during training. There is no magic here - the model is just trying to learn how to auto-regressively predict training set continuations.

Of course the humans who created the training set samples didn't create them auto-regressively - the training set samples are artifacts reflecting an external world, and knowledge about it, that the model is not privy to, but the model is limited to minimizing training errors on the task it was given - auto-regressive prediction. It has no choice. The "world model" (patterns) it has learnt isn't some magical grokking of the external world that it is not privy to - it is just the patterns needed to minimize errors when attempting to auto-regressively predict training set continuations.

Whether these training set predictive patterns result in the model performing as you might hope on an unseen text depends on the similarity of that text to samples in the training set.

Re:Things we learned about LLMs in 2024 by Jerrrry on Wednesday January 01, 2025 @08:00PM (#42570666)

  >Whether these training set predictive patterns result in the model performing as you might hope on an unseen text depends on the similarity of that text to samples in the training set.
>similarity

yes, except the computer can easily 'see' in more than 3 dimensions with more capability to spot similarities, and can follow lines of prediction (similar to chess) far more than any group of humans can.

that super-human ability to spot similarities and walk latent spaces 'randomly' -yet uncannily - has given rise to emergent phenomena that has mimicked proto-intelligence.

we have no idea what the ideas these tokens have embedded at different layers, and what capabilities can emerge now or at deployment time later, or given a certain prompt.

Re:Things we learned about LLMs in 2024 by HarHarVeryFunny on Thursday January 02, 2025 @07:39AM (#42573915)
The inner workings/representations of transformers/LLMs aren't a total black box - there's a lot of work being done (and published) on "mechanistic interpretability", especially by Anthropic.

The intelligence we see in LLMs is to be expected - we're looking in the mirror. They are trained to copy humans, so it's just our own thought patterns and reasoning being output. The LLM is just a "selective mirror" deciding what to output for any given input.

Re:Things we learned about LLMs in 2024 by Jerrrry on Thursday January 02, 2025 @11:20AM (#42575769)
Its mirroring the capability (if not currently the executive agency) of being able to convince people to do things. That alone gaps the barrier as social engineering is impossible to patch - harder than full proofing models against being jailbroken/used in an adversarial context.
Re:Things we learned about LLMs in 2024 by catalypso on Wednesday January 01, 2025 @02:08PM (#42568351)
I just tried it and I'm actually surprised with how well they work even with base64 encoded inputs.

This is assuming they don't call an external pre-processing decoding tool.

Re:Things we learned about LLMs in 2024 by simonw on Wednesday January 01, 2025 @02:17PM (#42568445)
The LLM UIs that integrate that kind of thing all have visible indicators when it's happening - in ChatGPT you would see it say "Analyzing..." while it ran Python code, and in Claude you would see the same message while it used JavaScript (in your browser) instead.

If you didn't see the "analyzing" message then no external tool was called.

Re:Things we learned about LLMs in 2024 by fennecbutt on Thursday January 02, 2025 @03:45PM (#42578657)
Idk if there is much code that "hasn't been written before".

Sure if you look at new project x then in totality it's a semi unique combination of code, but breaking it down into chunks that involve a couple lines, or a very specific context then it's all been done before.

Re:Things we learned about LLMs in 2024 by zkry on Wednesday January 01, 2025 @05:40AM (#42565210)
I'm pretty sure most people, developers especially, have had magical, life-changing experiences with LLMs. I think the problem is that they can't cant do these things reliably.

I get this sentiment from a lot of AI startups, that they have a product which can do amazing things, but due to its failure modes makes it almost useless as, to use an analogy from self-driving cars, the users have to still constantly pay attention to the road: you don't get a ride from Baltimore to New York where you can do whatever you please, you get a ride where you're constantly babysitting an autonomous vehicle, bored out of your mind, forced to monitor the road conditions and surrounding vehicles, lest the car make a mistake costing you your life.

To take the analogy farther, after experimenting with not using LLM tools, I feel that the main difference between the two modes of work is similar to driving a car and being driven by an autonomous care: you exert less mental effort, not, you get to your destination faster.

Another point of the analogy are things like Waymo. They really can do a great job of driving autonomously. But, they require a legible system of roads and weather conditions. There are LLM systems too that when given a legible system to work in can do a near perfect job.

Re:Things we learned about LLMs in 2024 by olivermuty on Wednesday January 01, 2025 @05:50PM (#42569969)
I mean… I agree that LLMs give only superficial value, but your analogy is plain wrong.

I drove 3600 km Norway to Spain in 2018 with only adaptive cruise. Then again in 2023 with autonomous highway driving (the kind where you keep a hand on the wheel for failure mode) and it was amaaaazing how big the difference was.

Re:Things we learned about LLMs in 2024 by zkry on Thursday January 02, 2025 @05:41AM (#42573353)
I get how I could be wrong on that front. I guess what I was trying to say was that there needs to be legible, predictable infrastructure for these AI systems to work well. I actually think that an LLM workflow in a constrained, well understood environment would be amazingly good too.

I've been driving a lot in Istanbul lately and I'm not holding my breath for autonomous vehicles any time soon.

Re:Things we learned about LLMs in 2024 by zestyping on Tuesday January 07, 2025 @01:16AM (#42619829)
Wait, can you say more about that? That doesn't match my intuitions very well, so I'd like to understand what made it such a big difference to you.

Were you using Tesla Autopilot? If I were using Autopilot, I'd have to be constantly watching out for its mistakes, which would probably be equally or more stressful compared to using adaptive cruise.

Re:Things we learned about LLMs in 2024 by tyre on Tuesday December 31, 2024 @07:27PM (#42562945)
antirez has written publicly, only a few weeks ago[0], about their experience working with LLMs. Partial quote:

> And now, at the end of 2024, I’m finally seeing incredible results in the field, things that looked like sci-fi a few years ago are now possible: Claude AI is my reasoning / editor / coding partner lately. I’m able to accomplish a lot more than I was able to do in the past. I often do more work because of AI, but I do better work.

>…

> Basically, AI didn’t replace me, AI accelerated me or improved me with feedback about my work

[0]: https://antirez.com/news/144

Re:Things we learned about LLMs in 2024 by JambalayaJimbo on Tuesday December 31, 2024 @06:17PM (#42562595)
Why would the author of Redis describe himself as “not a programmer”? That’s a little odd.
Re:Things we learned about LLMs in 2024 by harrisi on Tuesday December 31, 2024 @06:22PM (#42562620)
They didn't.

EDIT: antirez is the creator of redis, not mvkel.

Re:Things we learned about LLMs in 2024 by duggan on Tuesday December 31, 2024 @06:39PM (#42562696)
antirez is clearly going to be “Staff-plus” for almost any definition.

Can you clarify what you mean?

Re:Things we learned about LLMs in 2024 by cj on Tuesday December 31, 2024 @08:43PM (#42563300)
(Not original commenter) “Staff” engineer is typically one of the most senior and highest paid engineer titles in very large tech company. “Staff plus” is implying they are the best of the best.
Re:Things we learned about LLMs in 2024 by sarchertech on Tuesday December 31, 2024 @09:11PM (#42563448)
Staff plus just means staff or higher. Staff, senior staff, principal, mega ultra principal etc…
Re:Things we learned about LLMs in 2024 by cj on Tuesday December 31, 2024 @09:52PM (#42563589)
Outside of big tech, those titles aren’t common. Level X SWE vs staff vs principal doesn’t mean anything to a lot of people who aren’t in that orbit.
Re:Things we learned about LLMs in 2024 by SoftTalker on Wednesday January 01, 2025 @03:09PM (#42568857)
Yes when I started working, "staff" meant entry-level. My first job out of school was a "staff consultant." So I'm always tripped up when I see "staff" used to mean "very senior/experienced"
Re:Things we learned about LLMs in 2024 by lynguist on Thursday January 02, 2025 @07:05AM (#42573714)
Senior also somehow changed from meaning 10 years of experience to only 3 years of experience.
Re:Things we learned about LLMs in 2024 by sarchertech on Thursday January 02, 2025 @12:22AM (#42571897)
Sure, but my point is when someone says staff plus they mean staff or higher. They don’t mean higher than staff, or the best of the best staff engineers.

It just means anyone higher than a senior engineer.

Re:Things we learned about LLMs in 2024 by manmal on Wednesday January 01, 2025 @07:18AM (#42565593)
I’ve seen your comment below, but you did specify big tech as context in this parent comment, no? Or is „very large tech company“ not FAANG?

Google has Staff at L6, and their ladder goes up to L11. Apple‘s Staff pendant is ICT5, which is below ICT6 and Distinguished. Amazon has E7-E9 above Staff, if you count E6 as Staff. Netflix very recently departed from their flat hierarchy and even they have Principal above Staff.

Re:Things we learned about LLMs in 2024 by lr1970 on Wednesday January 01, 2025 @11:17AM (#42566937)
> Amazon has E7-E9 above Staff

Few clarifications:

Amazon labels levels with "L" rather than "E". Engineering levels are L4 -- L10. Weirdly enough, level L9 does not exist at Amazon. L8 (Director / Senior Principal Engineer) is promoted directly to L10 (VP / Distinguished Engineer)

Re:Things we learned about LLMs in 2024 by chikere232 on Wednesday January 01, 2025 @04:11AM (#42564892)
You should worry though if a helpful tool only seems to do a good job in areas you don't know well yourself. It's quite possible that the tool always does a bad job, but you can only tell when you know what a good job looks like.
Re:Things we learned about LLMs in 2024 by dicytea on Wednesday January 01, 2025 @04:48AM (#42565024)
I don't understand, you're replying in a thread where that very - super-experienced and productive low-level programmer - is talking about how he finds LLMs useful.
Re:Things we learned about LLMs in 2024 by Ferret7446 on Wednesday January 01, 2025 @04:53AM (#42565042)
I think that is more that a staff-plus engineer is going to be doing a lot more management than "actual work", and LLMs don't help much with management yet (until we get viable LLM managers shudder).

LLMs are like a pretty smart but overly confident junior engineer, which is what a senior engineer usually has to work with anyway.

An expert actually benefits more from LLMs because they know when they get an answer back that is wrong so they can edit the prompt to maybe get a better answer back. They also have a generally better idea of what to ask. A novice is likely to get back convincing but incorrect answers.

Re:Things we learned about LLMs in 2024 by scarface_74 on Wednesday January 01, 2025 @06:18AM (#42565368)
I know of no “staff plus” engineer (currently staff) that is spending a lot of time coding.

That wouldn’t be “working at your level” at the one BigTech company I’ve worked at and not even at the 600 person company I work at now

Re:Things we learned about LLMs in 2024 by egometry on Tuesday December 31, 2024 @05:21PM (#42562283)
To the un-sticking point: it's also great at letting people ask questions without being perceived as dumb

Tragically - admitting ignorance, even with the desire to learn, often has negative social reprocussions

Re:Things we learned about LLMs in 2024 by simonw on Tuesday December 31, 2024 @05:26PM (#42562311)
Asking "stupid" questions without fear of judgement is legit one of my favorite personal applications of LLMs.
Re:Things we learned about LLMs in 2024 by tkgally on Tuesday December 31, 2024 @06:32PM (#42562663)
That is one of the great strengths of LLMs for school education as well. Students often refrain from asking questions in class out of embarrassment at showing their ignorance or hesitation at interrupting the flow of the class. When used well, LLMs offer a good way for motivated learners to fill in the gaps in their understanding.

The pervasive problem of low student motivation won't be solved by LLMs, though. Human teachers will, I think, still be needed.

Re:Things we learned about LLMs in 2024 by foundart on Tuesday December 31, 2024 @08:36PM (#42563273)
Yes! In the time it would take to organize a question in a form that won’t be downvoted/closed on StackOverflow you can ask a whole series of LLM questions and learn quite a bit.
Re:Things we learned about LLMs in 2024 by james_marks on Tuesday December 31, 2024 @08:41PM (#42563290)
I find myself doing this all the time, as an experienced dev.

All the little nooks of missing knowledge are now very easy to fill in.

Re:Things we learned about LLMs in 2024 by littlestymaar on Tuesday December 31, 2024 @07:28PM (#42562951)
Most of the time it doesn't actually, and most people should definitely do it way more instead of pretending to understand thinks they don't, but this bad habit is probably gained thanks to the school system where asking a stupid question is going to get you mocked by your peers. The thing is, IRL your peers don't get to hear your stupid questions and knowledgeable people are happy to answer them no matter how "dumb" they are (or they don't like questions at all, and you'll bother them even if you asked interesting questions).

See https://danluu.com/look-stupid/

Re:Things we learned about LLMs in 2024 by wanderingmind on Wednesday January 01, 2025 @06:21AM (#42565380)
This appears to be an interesting social phenomena. Just wondering if the interaction with the LMM has also reduced our inhabitance to ask dumb questions, when interacting with other people as well.
Re:Things we learned about LLMs in 2024 by Ruxbin on Tuesday December 31, 2024 @07:41PM (#42563010)
May you expand how you did this? I'm seeing a number of apps that claim to do just this and there are number that are becoming super popular.

Not just the development of the code but the entire the thing from the code, infra, auth, cc payments, etc.

Re:Things we learned about LLMs in 2024 by mvkel on Tuesday December 31, 2024 @08:06PM (#42563123)
Planning to write a lengthy blog post on this. Will reply here.
Re:Things we learned about LLMs in 2024 by 8n4vidtmkvmk on Tuesday December 31, 2024 @10:05PM (#42563635)
For CC payments, just use Stripe. The docs are great!
Re:Things we learned about LLMs in 2024 by mellosouls on Tuesday December 31, 2024 @06:50PM (#42562763)
I interpreted it as saying that ymmv wrt the models you try and how you use them, and sole exposure to one that doesn't work for you can put you off the whole lot - in this case antirez finds Claude sonnet (with good prompting) very helpful, but gpt 4o (by far the best known due to ChatGPT), not so much and if the latter is representative of others experience it may be why many are still sceptical.
Re:Things we learned about LLMs in 2024 by HarHarVeryFunny on Tuesday December 31, 2024 @05:42PM (#42562396)
Did you need a Mac for that, or is it possible to use Linux to develop a Swift app targeting iOS?

Would you mind sharing which app you released?

Re:Things we learned about LLMs in 2024 by MYEUHD on Tuesday December 31, 2024 @06:00PM (#42562507)
You need macOS, which you can run in a VM (e.g. https://github.com/kholia/OSX-KVM ) or by setting up a hackintosh.
Re:Things we learned about LLMs in 2024 by fijiaarone on Tuesday December 31, 2024 @07:54PM (#42563069)
Strange that you don’t mention your product. Making too much money already?
Re:Things we learned about LLMs in 2024 by raydev on Tuesday December 31, 2024 @05:05PM (#42562212)
Which service/LLM performed the best for you?
Re:Things we learned about LLMs in 2024 by mvkel on Tuesday December 31, 2024 @08:10PM (#42563147)
Sonnet-3.5 seemed to churn out the best code, so I would default to that. If it got stuck in circular reasoning, 4o would usually resolve it. Then back to Sonnet.
Re:Things we learned about LLMs in 2024 by mvdtnz on Tuesday December 31, 2024 @10:00PM (#42563620)
> I built and shipped a Swift app to the App Store, currently generating $10,200 in MRR, exclusively using LLMs.

My experience is that people who claim they build worthwhile software "exclusively" using LLMs are lying. I don't know you and I don't know if you are lying, but I would be willing to bet my paycheck you are.

Re:Things we learned about LLMs in 2024 by csomar on Wednesday January 01, 2025 @02:22AM (#42564515)
They are also usually selling another AI-wrapper. I don't know the parent poster either but if your LLM product is generating $10k/month, your moat is really weak and you'll probably shut the f* up because your only moat is obscurity. Why risk that?
Re:Things we learned about LLMs in 2024 by jahnu on Wednesday January 01, 2025 @07:14AM (#42565579)
We shouldn’t assume the app created the customer base anew or solves a novel problem. Maybe this one does, we don’t know. But, what if the app is just an app version of a existing website store?

As an example I could imagine a clothing brand wanting an app that customers can install instead of using their phone browser. $10k/month in that context isn’t as surprising or impressive.

Re:Things we learned about LLMs in 2024 by csomar on Thursday January 02, 2025 @01:10AM (#42572135)
In which case the LLM contribution to the $10K/month is equivalent to hiring a mobile developer to build such an app which (given the implied simplicity) should be a few thousands one time cost. Not the $120K/month implied by PP. And don't get me wrong, paying a few dozen dollars to get a few thousand dollars worth of software is quite the value.
Re:Things we learned about LLMs in 2024 by mvkel on Wednesday January 01, 2025 @12:33PM (#42567514)
I hope someday that people will understand that you can use AI to build "boring" non-AI apps.
Re:Things we learned about LLMs in 2024 by csa on Wednesday January 01, 2025 @04:12PM (#42569346)
> I don't know the parent poster either but if your LLM product is generating $10k/month, your moat is really weak and you'll probably shut the f* up because your only moat is obscurity. Why risk that?

It sounds like they are doing productized consulting, so the relationship is the moat.

Re:Things we learned about LLMs in 2024 by mvkel on Wednesday January 01, 2025 @12:32PM (#42567510)
I mean, I'm pretty upfront on my personal site that I've built successful companies in the past. Not sure why I would lie about this one, especially when I'm admitting that I'm not doing the work :)

See comment above for more context.

Re:Things we learned about LLMs in 2024 by csa on Wednesday January 01, 2025 @04:11PM (#42569339)
It sounds like they are doing productized consulting, in which case the software doesn’t have to be particularly complex.

The relationship also builds a natural moat.

Re:Things we learned about LLMs in 2024 by yogrish on Tuesday December 31, 2024 @10:25PM (#42563717)
May I know what is the name of app that is built using LLM? 10k MRR is highly successful app.
Re:Things we learned about LLMs in 2024 by oblio on Wednesday January 01, 2025 @01:25AM (#42564310)
> I built and shipped a Swift app to the App Store, currently generating $10,200 in MRR, exclusively using LLMs.

That's great, but professional programmers are afraid of the future maintenance burden.

Re:Things we learned about LLMs in 2024 by mvkel on Wednesday January 01, 2025 @12:38PM (#42567548)
"maintenance burden" is introduced when a non-original programmer starts contributing to a repo, regardless of how objectively maintainable the code is.
Re:Things we learned about LLMs in 2024 by oblio on Wednesday January 01, 2025 @03:11PM (#42568872)
Everything in life is about degrees (or ranges, or orders of magnitude - whichever way you want to phrase it).
Re:Things we learned about LLMs in 2024 by archagon on Wednesday January 01, 2025 @03:43AM (#42564777)
Off topic, but I'm a bit confused. Your iOS apps as listed on your website are CarPrep and Brocly, neither of which appear to have notable review activity or buzz in the media. If the app you're referring to is one of these, the more interesting question (to me) is: how on Earth are you generating $10,200 MRR from it? Or is there another app that I'm missing?

(In my experience as an app developer, getting any traction and/or money from your app can be much more difficult than actually building it.)

Re:Things we learned about LLMs in 2024 by PurestGuava on Wednesday January 01, 2025 @09:02AM (#42566061)
> (In my experience as an app developer, getting any traction and/or money from your app can be much more difficult than actually building it.)

This. The app I built has maybe 50 downloads despite me trying quite hard to promote it. It's very difficult work, even with the app being completely free of charge (save for a donation button).

Re:Things we learned about LLMs in 2024 by mvkel on Wednesday January 01, 2025 @12:30PM (#42567497)
Those are just my silly personal projects, not businesses. The business I mentioned above is in the recruiting agency space, B2B SaaS. The app itself is not the thing being purchased per se, the point was it was built using LLMs.

$10K MRR isn't much; we're still validating PMF. We're carefully selecting paid customers at this point, not open for wide release, hence my vagueness. Just wanted to illustrate that building robust apps that have value are possible today.

Re:Things we learned about LLMs in 2024 by archagon on Wednesday January 01, 2025 @04:00PM (#42569255)
Thanks for the clarification!
Re:Things we learned about LLMs in 2024 by s1mplicissimus on Wednesday January 01, 2025 @01:16PM (#42567886)
Would be very interesting to have a look at this app that you wrote using only LLMs. Mind sharing the name?
Re:Things we learned about LLMs in 2024 by Tomte on Wednesday January 01, 2025 @03:20PM (#42568956)
I tried exactly that, a simple Todo-like app, without SwiftUI or Swift knowledge, and Sonnet 3.5 only gave me one syntax error after another. Now I‘m watching Paul Hudson‘s intro videos.
Re:Things we learned about LLMs in 2024 by chairmansteve on Wednesday January 01, 2025 @05:52PM (#42569974)
"I built and shipped a Swift app to the App Store, currently generating $10,200 in MRR, exclusively using LLMs".

What's the app?!!

Re:Things we learned about LLMs in 2024 by FooBarWidget on Tuesday December 31, 2024 @05:14PM (#42562250)
Why do people have such narrow views on what makes LLMs useful? I use them for basically everything.

My son throwing an irrational tantrum at the amusement park and I can't figure out why he's like that (he won't tell me or he doesn't know himself either) or what I should do? I feed Claude all the facts of what happened that day and ask for advice. Even if I don't agree with the advice, at the very least the analysis helps me understand/hypothesize what's going on with him. Sure beats having to wait until Monday to call up professionals. And in my experience, those professionals don't do a better job of giving me advice than Claude does.

It's weekend, my wife is sick, the general practitioner is closed, the emergency weekend line has 35 people in the queue, and I want some quick half-assed medical guidance that while I know might not be 100% reliable, is still better than nothing for the next 2 hours? Feed all the symptoms and facts to Claude/ChatGPT and it does an okay job a lot of the time.

I've been visiting Traditional Chinese Medicine (TCM) practitioner for a week now and my symptoms are indeed reducing. But TCM paradigm and concepts are so different from western medicine paradigms and concepts that I can't understand the doctor's explanation at all. Again, Claude does a reasonable job of explaining to me what's going on or why it works from a western medicine point of view.

Want to write a novel? Brainstorm ideas with GPT-4o.

I had a debate with a friend's child over the correct spelling of a Dutch word ("instabiel" vs "onstabiel"). Google results were not very clear. ChatGPT explained it clearly.

Just where is this "useless" idea coming from? Do people not have a life outside of coding?

Re:Things we learned about LLMs in 2024 by krapp on Tuesday December 31, 2024 @05:20PM (#42562279)
Yes people have lives outside of coding, but most people are able to manage without having AI software intercede in as much of their lives as possible.

It seems like you trust AI more than people and prefer it to direct human interaction. That seems to be satisfying a need for you that most people don't have.

Re:Things we learned about LLMs in 2024 by claar on Tuesday December 31, 2024 @05:29PM (#42562328)
Why do you postulate that "most people don't have" this need? I also use AI non-stop throughout my day for similar uses.

This feels identical to when I was an early "smart phone" user w/my palm pilot. People would condescend saying they didn't understand why I was "on it all the time". A decade or two later, I'm the one trying to get others to put down their phones during meetings.

My take? Those who aren't using AI continually currently are simply later adopters of AI. Give it a few years - or at most a decade - and the idea of NOT asking 100+ AI queries per day (or per hour) will seem positively quaint.

Re:Things we learned about LLMs in 2024 by krapp on Tuesday December 31, 2024 @05:47PM (#42562431)
>Those who aren't using AI continually currently are simply later adopters of AI. Give it a few years - or at most a decade - and the idea of NOT asking 100+ AI queries per day (or per hour) will seem positively quaint.

I don't think you're wrong, I just think a future in which it's all but physically and socially impossible to have a single thought or communication not mediated by software is fucking terrifying.

Re:Things we learned about LLMs in 2024 by FooBarWidget on Tuesday December 31, 2024 @05:33PM (#42562349)
When I'm done working, chased my children to properly finish their dinner, helped my son with homework, and putting them to bed, it's already 9+ PM — the only time of the day when I have free time. Just which human besides my wife can I talk to at that point? What if she doesn't have a clue either? All the professionals are only open when I'm working. A lot of the issues happen during the weekend, when professionals are closed. I don't want to disturb friends during the evening, and it's not like they have the expertise I need anyway.

LLMs are infinitely patient, don't think I am dumb for asking certain things, consider all the information I feed them, are available whenever I need them, have a wide range of expertise, and are dirt cheap compared to professionals.

That they might hallucinate is not a blocker most of the time. If the information I require is critical, I can always double check with my own research or with professionals (in which case the LLM has already primed me with a basic mental model so that I can ask quick, short, targeted questions, which saves the both of us time, and me money). For everything else (such as my curiocity on why TCM works, or the correct spelling of a word), LLMs are good enough.

Re:Things we learned about LLMs in 2024 by vbezhenar on Wednesday January 01, 2025 @03:50AM (#42564809)
You are supposed to have connections with knowledgeable people, so you can call them and ask for advice. That's how it works without computers.
Re:Things we learned about LLMs in 2024 by FooBarWidget on Wednesday January 01, 2025 @11:56AM (#42567258)
Did you miss the parts where I said that I only have time when they're closed, and they're only open when I'm most busy?

Have you never seen knowledgeable people get things wrong, and having to verify them?

Did you miss the part where they cost money, and I better come in as prepared as possible?

I really don't get these knee-jerk averse reactions. Are people deliberately reading past my assertions that I double check LLM outputs for everything critical?

Re:Things we learned about LLMs in 2024 by CRConrad on Monday January 06, 2025 @10:42AM (#42611483)
> LLMs are infinitely patient, don't think I am dumb for asking certain things

We don't know that. They could be laughing their ass off at you without telling you.

Re:Things we learned about LLMs in 2024 by tokai on Tuesday December 31, 2024 @06:51PM (#42562767)
This reads like satire to me. Scarry that it isn't.
Re:Things we learned about LLMs in 2024 by signatoremo on Tuesday December 31, 2024 @08:55PM (#42563365)
Huh? The GP makes perfect sense. I’d never trust LLMs blindly, but I wouldn’t hesitate to ask them about any topic. “Trust but verify” is often said about human beings. Perhaps “distrust but ask and verify” is the mantra applicable for LLMs.
Re:Things we learned about LLMs in 2024 by raincole on Tuesday December 31, 2024 @11:11PM (#42563891)
I too read it as satire at first, but after thinking twice I think it's a quite reasonable take. I've added "utilize LLM more in my daily life outside programming" to my new year resolution.
Re:Things we learned about LLMs in 2024 by danielbln on Wednesday January 01, 2025 @07:44AM (#42565690)
I had the flu at the beginning of December, with high fever, the whole nine yards. Keeping a running log with Claude in which I shared temperature readings, medications etc. has been so useful. If nothing else it's the world's most sophisticated rubber duck / secretary, but that's quite useful in many daily life situations on its own. Caveats apply etc.
Re:Things we learned about LLMs in 2024 by FooBarWidget on Wednesday January 01, 2025 @01:51AM (#42564405)
I'm guessing that mindset is what cause some people to find this scary. I see a new tool and opportunities. Like all tools, it has drawbacks and caveats, but when wielded properly, it can give me more choice. I suspect some others focus too much on flaws and don't bother looking for opportunities. They are expecting a holy grail: if it's not perfect then it's useless.

It's like people who proclaim that Linux as a whole is a useless toy because it doesn't run their favorite games or favorite Windows app. They focus on this one flaw and miss all the opportunities.

Many of these people seem to advocate trusting human professionals. Do you have any idea how often human professionals do a half-assed job, and I have to verify them rather than blindly trusting them? The situation is not that much different from LLMs.

Professionals making mistakes do not make them useless. Grandma, with all her armchair expertise, is often right and sometimes wrong, and that does not make her useless either.

Why let perfect be the enemy of good?

Re:Things we learned about LLMs in 2024 by BlueTemplar on Wednesday January 01, 2025 @07:49AM (#42565713)
Grandma has a reason to care about you.

At the opposite, my trust of Russian / Chinese / USian platforms is low enough that I consider it my duty to publicly shame people that still use them in 2025.

(With some caveats of course, for instance HN is not a yet negative to the world. Yet.)

There's also the question of stickiness of habits : your grandmas are for life, human professionals you might have a shallow enough relationship with that switching them might be relatively easy, while it might be very hard to stop smoking or to stop using Github once you started smoking / create an account.

Re:Things we learned about LLMs in 2024 by FooBarWidget on Wednesday January 01, 2025 @12:00PM (#42567284)
You view Github and LLMs as a trap that deliberately give you malicious advice or even brainwash you into addiction? If you view things that way then it's no surprise that you are averse to LLMs (and Github). But frankly I find that entire view to be absurd and overly cynical.
Re:Things we learned about LLMs in 2024 by jiggawatts on Tuesday December 31, 2024 @05:30PM (#42562338)
At the risk of sounding impolite or critical of your personal choices: this, right here, is the problem!

You don’t understand how medicine works, at any level.

Yet you turn to a machine for advice, and take it at face value.

I say these things confidently, because I do understand medicine well enough to not to seek my own answers. Recently I went to a doctor for a serious condition and every notion I had was wrong. Provably wrong!

I see the same behaviour in junior developers that simply copy-paste in whatever they see in StackOverflow or whatever they got out of ChatGPT with a terrible prompt, no context, and no understanding on their part of the suitability of the answer.

This is why I and many others still consider AIs mostly useless. The human in the loop is still the critical element. Replace the human with someone that thinks that powdered rhino horn will give them erections, and the utility of the AI drops to near zero. Worse, it can multiply bad tendencies and bad ideas.

I’m sure someone somewhere is asking DeepSeek how best to get endangered animals parts on the black market.

Re:Things we learned about LLMs in 2024 by FooBarWidget on Tuesday December 31, 2024 @05:56PM (#42562481)
No. Where do you read that I take it at face value? I literally said that I expect Claude to give me "half-assed" medical guidance. I merely said that that is still better than having no clue for the next 2 hours while I wait on the phone with 35 people in front of me, which is completely different from "taking medicine advice at face value". It's not like I will let my wife drink bleach just because Claude told me to. But if it tells me that it's likely an ear infection then at least I can discuss the possibility with the doctor.

So I am curious about how TCM works. So what if an LLM hallucinates there? I am not writing papers on TCM or advising governments on TCM policy. I still follow the doctor's instructions at the end of the day.

For anything really critical I already double check with professionals. As you said, human in the loop is important. But needing human in the loop does not make it useless.

You are letting perfect be the enemy of good. A half-assed tax advice with some hallucinations from an LLM is still useful, because it will prime me with a basic mental model. When I later double check the whole thing with a professional, I will already know what questions to ask and what direction I need to explore, which saves time and money compared to going in with a blank slate.

The other day I had Claude advice me on how to write a letter to a judge to fight a traffic fine. We discuss what arguments to make, from what perspective a judge will see things, and thus what I should plead for. The traffic fine is a few hundred euros: a significant amount, but barely an hour worth of a real lawyer's fee. It makes absolutely no sense to hire a real lawyer here. If this fails, the worst thing that can happen is that I won't get my traffic fine reimbursed.

There is absolutely nothing wrong with using LLMs when you know their limits and how to mitigate them.

So what if every notion you learned about medicine from LLMs is wrong? You learn why they're wrong, then next time you prompt/double check better, until you learn how to use it for that field in the least hallucinationatory way. Your experience also doesn't match mine: the advice I get usually contains useful elements that I then discuss with doctors. Plus, doctors can make mistakes too, and they can fail to consider some things. Twitter is full of stories about doctors who failed to diagnose something but ChatGPT got it right.

Stop letting perfect be the enemy of good. Occasionally needing human in the loop is completely fine.

Re:Things we learned about LLMs in 2024 by fragmede on Tuesday December 31, 2024 @10:10PM (#42563659)
To be fair though, humanity doesn't know how some medicines work at a fundamental level either. The method of action for Tylenol, lithium, and metformin, among others isn't fully understood.
Re:Things we learned about LLMs in 2024 by jiggawatts on Tuesday December 31, 2024 @10:29PM (#42563746)
True, but modern "western"[1] medicine is not about the specific chemicals used, or even knowing how they exactly work at a chemical level, but the process for identifying what does and what does not work. It's an "evidence based" science with with experiments designed to counter known biases such as the placebo effect. Much of what we consider modern medicine was developed before we were entirely sure that atoms actually existed!

[1] It isn't actually western, because it's also used in the east, middle-east, south, both sides of every divide, etc... In the same sense, there is no "western chemistry" as an alternative to "eastern alchemy". There's "things that work" versus "things that make you feel slightly better because they're mild narcotics or stimulants... at best."

(I don't want to focus too much on Chinese herbal medicine, because I see the same cargo-culting non-scientific thinking in code development too. I've lost count of the number of times I've seen an n-tier SPA monstrosity developed for something that needed a tiny monolithic web app, but mumble-mumble-best-mumble-practices.)

Re:Things we learned about LLMs in 2024 by FooBarWidget on Wednesday January 01, 2025 @01:55AM (#42564420)
"Western medicine" (which is exactly what it is called in China, to contrast with TCM) is shorthand for "practices invented in the west". That these methods chase universal truths, or are practiced world-wide, do not make them "non-west" in terms of origin.

The Chinese call the practice of truth seeking, in a more broader sense (outside of medicine) just "science".

"Western" medicine is also not merely the practice of seeking universal medical truth. It is also a collection of paradigms that have been developed in its long history. Like all paradigms, there are limits and drawbacks: phenomena that do not fit well. Truth seeking tends to be done on established paradigms rather than completely new ones.

The "western" prefix is helpful in contrasting it with TCM, which has a completely different paradigm. Many Chinese, myself included, have the experience that there are all sorts of ailments that are not meaningfully solved by "western" medicine practitioners, but are meaningfully solved by TCM practitioners.

Re:Things we learned about LLMs in 2024 by CRConrad on Monday January 06, 2025 @10:40AM (#42611460)
Scary. Reads rather like you're well on your way to replace basic life skills with reliance on LLMs.
Re:Things we learned about LLMs in 2024 by karmakaze on Tuesday December 31, 2024 @05:34PM (#42562361)
We're at the "computers play chess badly" stage. Then we'll hit the Deep Thought (1988) and Deep Blue (1995-1997) stages, but still saying that solving Go won't happen for 50+ years and that humans will continue to be better than computers.

The date/time that divides my world into before/after is AlphaGo v Lee Sedol game 3 (2016). From that time forward, I don't dismiss out of hand speculations of how soon we can have intelligent machines. Ray Kurzweil date of 2045 is as good as any (and better than most) for an estimate. Like Moore's (and related) Laws, it's not about how but the historical pace of advancements crossing a fairly static point of human capability.

Application coding, requires much less intelligence than playing Go at these high levels. The main differences are concise representation and clear final outcome scoring. LLMs deal quite well with the fuzziness of human communications. There may be a few more pegs to place but when seems predictably unknown.

Re:Things we learned about LLMs in 2024 by kromem on Tuesday December 31, 2024 @05:51PM (#42562458)
Both new Sonnet and Haiku have a masking overhead.

Using a few messages to get them out of "I aim to be direct" AI assistant mode gets much better overall results for the rest of the chat.

Haiku is actually incredibly good at high level systems thinking. Somehow when they moved to a smaller model the "human-like" parts fell away but the logical parts remained at a similar level.

Like if you were taking meeting notes from a business strategy meeting and wanted insights, use Haiku over Sonnet, and thank me later.

Re:Things we learned about LLMs in 2024 by atombender on Tuesday December 31, 2024 @06:56PM (#42562778)
Is there a way to use this in Jetbrains IDEs? (I've not been impressed with their AI Assistant.) There are a few plugins, but from the reviews they all seem kind of mediocre.
Re:Things we learned about LLMs in 2024 by cpursley on Tuesday December 31, 2024 @07:18PM (#42562900)
Try Cursor. I’m serious.
Re:Things we learned about LLMs in 2024 by atombender on Tuesday December 31, 2024 @07:20PM (#42562915)
I'm sure it's good, but that's not what I'm asking about.
Re:Things we learned about LLMs in 2024 by cube2222 on Tuesday December 31, 2024 @08:55PM (#42563364)
I personally use the Zed editor AI assistant integration with Sonnet for anything AI-related, while using a JetBrains IDE for coding / code reading, side-by-side.

I haven’t found anything comparably good for JetBrains IDEs yet, but I’m also not switching to something else as my main editor.

Re:Things we learned about LLMs in 2024 by Sn0wCoder on Tuesday December 31, 2024 @11:52PM (#42564045)
I use IntelliJ as my main coding tool but also use VSCode and Sublime text. If you have access to local LLMs or have an API key for some the Continue Plugin (basically Cursor but can use in IntelliJ) is the Best of the Best for IntelliJ (IMO). I have a box running some local models including Phind and StarCoder (plus some small embeddings) and have been super happy with the end product. The next up is Google Gemini Code Assist has been the best of the IntelliJ (non-configured) AI tools I have tried. There are better ones out there but IMO not for IntelliJ. It's still free for a few more weeks and I have been using it since the free release, fun to use. Can pre-prompt, say you are an expert XXX, please be funny, fill in the rest of your regular prompts. The Co-Pilot I use for work is very limited and will only answer coding questions. I tried to tell it that it was my coding buddy, and its name was Phil and told me it cannot have a personality or be funny. I believe the paid personal Co-Pilot allows you to choose which LLM it uses (I cannot confirm). The Phind VSCode plugin works really well. Also, the Phind coding models are on par with some of the other big ones and free if you have a subscription (or run locally). Sublime is around to open those GIG+ files as VSCode chocks and not worth the RAM of opening another IntelliJ.

Each task / programming language / query requires trying different LLM models and novel ways of prompting. If it's not work-related (or work pays for the one you use) sending as much of the code as relevant also helps the answers be more useful.

Most of the people I meet that say LLMs are not useful have only tried one (flavor / plugin), do not know how to pre-prompt or prompt, and do not give the tools a chance. Try one or two things, say yep, it's not good and give up.

Still hard for me to admit that Prompt Engineering is a profession, but it's the same as Google Fu. Once you learn it you can become an LLM Ninja!

I do not believe LLMs are coming for my job (just yet) but do believe they are going to be able to replace some people, are useful and those that do not use them will be at a disadvantage.

Re:Things we learned about LLMs in 2024 by Too on Wednesday January 01, 2025 @04:36AM (#42564992)
Github copilot plugin is decent. It's not going to write a whole app for you, but it accelerates repetitive stuff, can give suggestions you didn't think of or save you a trip to the documentation.
Re:Things we learned about LLMs in 2024 by qwertox on Tuesday December 31, 2024 @07:22PM (#42562926)
LLMs have given computers the ability to communicate with us in natural language, we didn't have that before at this level. In order to do this, they've been fed with a lot of coherent stuff and give the impression of being coherent, but we know they're just statistical machines. But at least they can now communicate naturally with us, so now we have that infrastructure available, as we do have TTS or ASR or monitors and keyboards available. It's still up to us to now make proper agents out of them. Agents for the software we've been using for decades. They can take over a lot of tedious work for us.
Re:Things we learned about LLMs in 2024 by salawat on Tuesday December 31, 2024 @09:44PM (#42563565)
Why are you pasting huge chunks of potentially crown jewels code into a 3rd party service where prompts are going to most likely be turned into training/surveillance material?
Re:Things we learned about LLMs in 2024 by simonw on Tuesday December 31, 2024 @09:50PM (#42563584)
A lot of vendors promise not to train on input to their models. I choose to believe those promises.
Re:Things we learned about LLMs in 2024 by askl56 on Tuesday December 31, 2024 @10:14PM (#42563672)
A scorpion, not knowing how to swim, asked a frog to carry it across the river. “Do I look like a fool?” said the frog. “You’d sting me if I let you on my back!”

“Be logical,” said the scorpion. “If I stung you I’d certainly drown myself.”

“That’s true,” the frog acknowledged. “Climb aboard, then!” But no sooner than they were halfway across the river, the scorpion stung the frog, and they both began to thrash and drown. “Why on earth did you do that?” the frog said morosely. “Now we’re both going to die.”

“I can’t help it,” said the scorpion. “It’s my nature.”

Re:Things we learned about LLMs in 2024 by zahlman on Tuesday December 31, 2024 @10:24PM (#42563715)
>They are also great at doing boring tasks for which you can provide perfect guidance (but that still would take you hours)

All the tasks I can think of dealing with on my own computer that would take hours, a) are actually pretty interesting to me and b) would equally well take hours to "provide perfect guidance". The drudge work of programming that I notice comes in blocks of seconds at a time, and the mental context switch to using an LLM would be costlier.

Re:Things we learned about LLMs in 2024 by worldsayshi on Tuesday December 31, 2024 @10:42PM (#42563804)
I ponder if LLM:s are very useful but at a quite narrower set of tasks than we expect. Like fuzzy manipulation of logical specifications.

I.e. over time it constitute a fundamental shift in how we interact with abstractions in computers. The current fundamentals will still remain but they will become increasingly malleable. Details in code will become less important. Architecture will become increasingly important. But at the same time the cost of refactoring or changing architecture will quickly drop.

Any details that are easily lost when passing through an LLM will be details that have the highest maintenance cost. Any important details that can be retained by an LLM can move up and down the ladder of abstraction at will.

Can an LLM based solution maintain software architectures without introducing noise? The answer to that is the difference between somewhat useful and game changing.

Re:Things we learned about LLMs in 2024 by mikehollinger on Wednesday January 01, 2025 @12:50AM (#42564225)
> 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

> a key thing with LLMs is that their ability to help, as a tool, changes vastly based on your communication ability.

I still hold that the innovations we've seen as an industry with text transfer to the data from other domains. And there's an odd misbehavior with people that I've now seen play out twice -- back in 2017 with vision models (please don't shove a picture of a spectrogram into an object detector), and today. People are trying to coerce text models to do stuff with data series, or (again!) pictures of charts, rather than paying attention to timeseries foundation models which directly can work on the data.[1]

Further, the tricks we're seeing with encoder / decoder pipelines should work for other domains. And we're not yet recognizing that as an industry. For example, whisper or the emerging video models are getting there, but think about multi-spectral satellite data, fraud detection (a type graph problem).

There's lots of value to unlock from coding models. They're just text models. So what if you were to shove an abstract syntax tree in as the data representation, or the intermediate code from LLVM or a JVM or whatever runtime and interact with that?

[1] https://huggingface.co/ibm-granite/granite-timeseries-ttm-r1 - shout-out to some former colleagues!

Re:Things we learned about LLMs in 2024 by simonw on Wednesday January 01, 2025 @12:54AM (#42564233)
Andrej Karpathy: https://twitter.com/karpathy/status/1835024197506187617

> It's a bit sad and confusing that LLMs ("Large Language Models") have little to do with language; It's just historical. They are highly general purpose technology for statistical modeling of token streams. A better name would be Autoregressive Transformers or something.

> They don't care if the tokens happen to represent little text chunks. It could just as well be little image patches, audio chunks, action choices, molecules, or whatever. If you can reduce your problem to that of modeling token streams (for any arbitrary vocabulary of some set of discrete tokens), you can "throw an LLM at it".

Re:Things we learned about LLMs in 2024 by vbezhenar on Wednesday January 01, 2025 @03:19AM (#42564701)
But I need enormous amounts of learning data and enormous amount of computing to learn new models, right? So it's kind of useless advice for most people who can't just parse github repositories and teach their new model using AST tokens. They have to use existing opensourced models or API and those happened to use text.
Re:Things we learned about LLMs in 2024 by monero-xmr on Wednesday January 01, 2025 @01:03AM (#42564255)
The environmental arguments are hilarious to me as a diehard crypto guy. The ultimate answer to “waste” of electricity arguments is that energy is a free market and people pay the price if it’s useful for them. As long as the activity isn’t illegal then training LLMs or mining bitcoins, it doesn’t matter. I pay for the electricity I use.
Re:Things we learned about LLMs in 2024 by Eisenstein on Wednesday January 01, 2025 @01:28AM (#42564318)
Do you think that it we should make it illegal to mine coins if the majority of people think the environmental cost is too high?
Re:Things we learned about LLMs in 2024 by monero-xmr on Wednesday January 01, 2025 @04:32AM (#42564980)
If a law is passed then that’s the law
Re:Things we learned about LLMs in 2024 by adwn on Wednesday January 01, 2025 @06:21AM (#42565382)
One argument against that line of thinking is that energy production has negative externalities. If you use a lot of electricity, its price goes up, which incentivizes more electricity production, which generates more negative externalities. It will also raise the costs for other consumers of electricity.

Now that alone is not yet an argument against crypto currencies, and one person's frivolous squandering of resources is another person's essential service. But you can't simply point to the free market to absolve yourself of any responsibility for your consumption.

Re:Things we learned about LLMs in 2024 by monero-xmr on Wednesday January 01, 2025 @08:46AM (#42565981)
I greatly despise video games. Why is that not a waste of energy? If you are entertained by something, even if it serves no human purpose other than entertainment, is that not a valid use of electricity?
Re:Things we learned about LLMs in 2024 by specialist on Thursday January 02, 2025 @12:31PM (#42576484)
Unintentionally, the energy demands of cryptocurrencies, and data centers in general, have finally motivated utilities (and their regulators) to finally start building out the massive new grid capacity needed for our glorious renewable energy future.

Acknowledging that facilitating scams (eg pig butchering) are cryptocurrency's primary (sole?) use case, I'm willing to look the other way if we end up with the grid we need to address climate crisis.

Re:Things we learned about LLMs in 2024 by monero-xmr on Friday January 03, 2025 @12:25AM (#42582768)
To pretend romance / affinity scams and crime were created by crypto is absurd. It’s fair to argue crypto made crime more efficient, but it also made the responsible parties quicker to patch holes.

The primary use case of crypto is to protect wealth from a greedy, corrupt, money-printing state. Everything else is a sideshow

Re:Things we learned about LLMs in 2024 by specialist on Friday January 03, 2025 @08:51AM (#42585633)
> primary use case of crypto is to protect wealth

Merely trading governments for corporations.

> Everything else is a sideshow

Agreed. Crypto is endlessly amusing.

Re:Things we learned about LLMs in 2024 by monero-xmr on Friday January 03, 2025 @09:26AM (#42585903)
What corporation made bitcoin?
Re:Things we learned about LLMs in 2024 by specialist on Saturday January 04, 2025 @11:51PM (#42599859)
Apologies, I assumed you knew what cryptocurrency is and how it works. My bad.

I'm really not well suited to explain this stuff. Here's an article for a general (layperson) audience to help you on your journey. https://www.cbsnews.com/news/cryptocurrency-bitcoin-virtual-...

Happy hunting!

Re:Things we learned about LLMs in 2024 by monero-xmr on Sunday January 05, 2025 @01:37AM (#42600173)
I have been intimately involved with cryptocurrency since 2010
Re:Things we learned about LLMs in 2024 by miki123211 on Wednesday January 01, 2025 @06:19AM (#42565371)
> But there is more: a key thing with LLMs is that their ability to help, as a tool, changes vastly based on your communication ability. The prompt is the king to make those models 10x better than they are with the lazy one-liner question.

People keep saying this, and there are use cases for which this is definitely the case, but I find the opposite to be just as true in some circumstances.

I'm surprised at how good LLMs are at answering "me be monkey, me have big problem with code" questions. For simple one-offs like "how to do x in Pandas" (a frequent one for me), I often just give Claude a mish-mash of keywords, and it usually figures out what I want.

An example prompt of mine from yesterday, which Claude successfully answered, was "python sha256 of file contents base64 safe for fs path."

With a system prompt to make Claude's output super brief and a command to execute queries from the terminal via Simon Willison's LLM tool, this is extremely useful.

Re:Things we learned about LLMs in 2024 by mewpmewp2 on Wednesday January 01, 2025 @06:58AM (#42565514)
Using the correct keywords like you did is part of communication though.

Good communication with LLMs is the least keywords used to make it deducible for LLM what you exactly want.

Re:Things we learned about LLMs in 2024 by EagnaIonat on Wednesday January 01, 2025 @07:42AM (#42565681)
> Good communication with LLMs is the least keywords used to make it deducible for LLM what you exactly want.

I am not sure that is the case, at least with a large number of LLMs. CO-STAR and TIDD-EC are much about structure and explanation than brevity.

Re:Things we learned about LLMs in 2024 by freehorse on Wednesday January 01, 2025 @09:21AM (#42566157)
Finding what works for an llm and what not is also part of communication skills.

Though I do not have a good idea what is _bad_ communication with an llm. People say that sometimes, but when specific examples arise I do not see really anything more than limitations of llms (and the improvements they often suggest do not do anything either). So it would be good to have some more concrete examples, unless that is about inability to communicate a problem in general, stemming from actual inability to _understand_ the problem. Also a lot change in time, I think in the past one had to really coddle an llm "You are the best expert in python in the world!" but I am not sure that is that important nowadays.

Re:Things we learned about LLMs in 2024 by mewpmewp2 on Thursday January 02, 2025 @09:32AM (#42574726)
Bad communication => being too ambiguous, expecting LLM to understand you through that ambiguity and then not being satisfied when it didn't.

Bad communication: "My webapp doesn't work"

Good communication: "Nextjs, [pasted error]"

Bad communication is giving irrelevant information, or being too ambiguous, not providing enough or correct detail.

Then another example of good communication and efficiency in my view is for example "ts, fn leftpad, no text, code only".

I myself can understand what it means when someone was to prompt it and LLM can understand such query for all domains.

Although if I was using Copilot I would just write the bare minimum to trigger the auto complete I want so

const leftPad =

is probably enough.

Re:Things we learned about LLMs in 2024 by abhijeetpbodas on Wednesday January 01, 2025 @06:57AM (#42565509)
> ask very precise questions explaining the background

IME, being forced to write about something or verbally explaining/enumerating things in detail _by itself_ leads to a lot of clarity in the writer's thoughts, irrespective of if there's an LLM answering back.

People have been doing rubber-duck-debugging since long. The metaphorical duck (LLMs in our context), if explained to well, has now started answering back with useful stuff!

Re:Things we learned about LLMs in 2024 by danielbln on Wednesday January 01, 2025 @08:47AM (#42565990)
One thing LLMs have been incredibly strong even since gpt-3.5 is being the most advanced non-human rubber duck, and while they can do plenty more, that alone provides (me at least) with tremendous utility.
Re:Things we learned about LLMs in 2024 by isoprophlex on Wednesday January 01, 2025 @07:05AM (#42565541)
Super interesting that my experience mirrors exactly what you are writing... except for me finding Claude to be almost useless (often misunderstands me, gives answers that are plain wrong) and 4o to be a very helpful, if not somewhat dull, jack-of-all trades in helping me be a cruise control for the mind.

I could only ever really jam with 4o.

Makes me wonder if there's personal communication preferences at play here.

Re:Things we learned about LLMs in 2024 by weMadeThat on Wednesday January 01, 2025 @07:29AM (#42565639)
> They work great to explore what is at the borders of your knowledge.

But not at exploring what is at the border of knowledge itself. And by converging on the conventional, LLMs actually lead you away from anything that actually extends.

> doing boring tasks for which you can provide perfect guidance

That's true but you never need an LLM for that. There are wonderful scripts written by wonderful people and provided for free almost all the time and for those who search in the right places. LLM companies benefit/profit of these without providing anything in return.

They are worse than people who grab FOSS and turn it into overpriced and aggressively marketed business models and services or people who threaten and sue FOSS for being better and free alternatives to their bloated and often "illegally telemetric" services.

> able to accelerate you

True, but you leave too much for data brokers and companies like Meta to abuse and exploit in the future. All that additional "interactional data" will do so much worse to humanity than all those previous data sets did in elections, for example, or pretty much all consumer markets. They will mostly accelerate all these dimwitted Fortune 5000 companies that have sabotaged consumers into way too much dumb shit - way more than is reasonable or "ok". And educated, wealthy and or tech-savvy people won't be able to avoid/evade any of that. Especially when it's paired with meds, drugs, foods, biases, fallacies, priming and so on and all the knowledge we will gain on bio-chemical pathways and human liability to sabotage.

They are great for coders, of course, everyone can be an army of clone-warriors with auto-complete on steroids now and nobody can tell you what to do with all that time that you now have and all that money, which, thanks to all of us but mostly our ancestors, is the default. The problem is the resulting hyper-amplified, augmented financial imbalance. It's gonna fuck our species if all the technical people don't restore some of that balance, and everybody knows what that means and what must be done.

Re:Things we learned about LLMs in 2024 by aleph_minus_one on Wednesday January 01, 2025 @08:17AM (#42565831)
> 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.

I see much deeper problems. Just to give two examples:

- I asked various AIs concerning explanations of proofs of some deep (established) mathematical theorems: the explanations were to my understanding very hallucinated, and thus worse than "obviously wrong". I also asked for literature references for some deep mathematical theory frameworks: bascially all of the references were again hallucinated.

- I asked lots of AIs on https://lmarena.ai/ to write a suitably long text about some political topic that is quite controversial in my country (but does have lots proponents even in a very radical formulation, even though most people would not use such a radical formulation in public). All of the LLMs that I checked refused or tried to indoctrinate me that this thesis is wrong. I did not ask the LLM to lecture me, but I gave it a concrete task! Society is deeply divided, so if the LLM only spreads propaganda of its political teaching, it will be useless for many tasks for a very significant share of the society.

Re:Things we learned about LLMs in 2024 by ddgflorida on Wednesday January 01, 2025 @10:40AM (#42566656)
Definitely not a "useless toy" with the right use case. It's great at code snippets, scripts, etc. It's an assistant.
Re:Things we learned about LLMs in 2024 by vasco on Wednesday January 01, 2025 @12:12PM (#42567377)
Most people consider their own brain useless and don't use it, so it's not strange that they do the same with AI. How many people just refuse to learn how to parallel park, a new language, calculus or even basic arithmetic, "because they aren't good at it".
Re:Things we learned about LLMs in 2024 by ta12653421 on Thursday January 02, 2025 @07:09AM (#42573735)
ClaudeAI ++1000