Hacker News Reader

Comment by scopeh | Hacker News Reader

Lets make ourselves redundant.

At least I won't have to relearn JS every 2 weeks.

Don't worry, in 5 years it will just be another layer in the JS dev stack, so then not only the version of npm, dependencies, docker, and 3 API keys have to match but you'll also need the correct commit of the 20GB LLM so the build doesn't fail. All for the sake of simplicity and increased productivity, of course.

We’ll have dependency files for LLMs in our mixture of experts config and we’ll get paged at 2am to update a version of an LLM because there’s a new social engineering CVE making it vulnerable to disclosing secrets.

let chatgpt fix our dependency issues

required dependency: leftpad-ai-gpt4

These little demos of toy UIs are cute but humans can still hold the context of a whole codebase in their heads.

We're not quite at the level (yet) of feeding a whole codebase to an LLM and making it add features or make changes while understanding the big picture of the problem being solved, being consistent with the design principles and coding style of the overall existing codebase. And I'm not even talking about creating complex UIs where performance matters

Another issue I've ran into a lot is staleness of the knowledge the LLM was trained on, a lot of libraries and frameworks get really frequent, quite often breaking changes, and LLMs have a cutoff date.

Try using ChatGPT for something like Godot's GDScript, it will always try to use old Godot v3 style scripting because that's what it's been taught, and the whole documentation for Godot v4 is not something small enough to just fit into context

Maybe this would be a better fit for some agent type workflow where it can decide what to lookup from the documentation and then retrieve it, but it also needs to know and decide what to look up and how. There is still a lot to figure out

> We're not quite at the level (yet) of feeding a whole codebase to an LLM and making it add features or make changes while understanding the big picture of the problem being solved

We are one step away from that. All we need is a more advanced form of fine tuning.

lol, this magical thinking; also not AI, it's ML

ML is a kind of AI

nope

Sorry to do this to you, but you're actually incorrect.

sorry to dither your ego, but it's not; prove it, but i guess lying to yourself is easier than accepting you're wrong

If there is one good thing going to come out of EVEN the fairly clumsy LLMs, it is that we probably can forget about this js frontend framework crap and can focus on work instead of figuring out what the taste-du-jour is. It won't matter; the LLM will translate it.

Probably not. Instead we’ll be stuck using the old frameworks driver because LLMs won’t be able to learn anything new without years of stack overflow examples.

Already I bet stack overflow usage has gone down because LLMs can help fixing bugs.

I think the documentation, open source code, and code examples are more important training sets.

And in. my experience the code is often maybe 95% correct, so there will be a greater premium on expert developers who can spot and fix bugs (with the aid of LLMs, since stack overflow will no longer have any answers since no one will use it having moved to LLMs)

Stackoverflow has less that 50% of the traffic now than it used to a few years ago.

I 10000% agree.

More like - let's give ourselves better tools. The people who hire us won't be able to build this stuff themselves no matter how good an AI you give them. The only developers who will lose their job are ones who fail to embrace AI.

You don't have to now too

Much like cockroaches JS will survive a nuclear explosion

Reply on news.ycombinator.com