Things we learned about LLMs in 2024

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]