← Back to context

Comment by itake

17 hours ago

But… the models will fall behind. As libraries and languages and tool calling updates or the world knowledge changes, the models decay.

Personally, I don’t like the change, but it’s just how technology works so I’d rather move with the flow than try to stick my foot down and freeze time.

6 comments

itake

Reply
hypfer  12 hours ago

> But… the models will fall behind.

Yes but why does that matter? If I am happy with its capabilities now, I will continue being happy with its capabilities in the future.

Yes, it cannot do the newest magic shit, but why does that matter? It can still do everything that existed up until that point, which is _a lot_.

Eventually, you might also need something new, but it's not like the world shifts over all problems that exist from <old> to <new> and any tech for <old> problems suddenly becomes obsolete?

  • itake  11 hours ago

    ideally, the software produced should include the latest security patches.

    If the model prefers a version of Ruby or node with an RCE, I guess you can burn tokens to teach the model how to avoid the introducing the vulnerability into your code?

    That feels quite tedious and token inefficient..

    • hypfer  11 hours ago

      I'm sorry, but.. are you being serious?

      Yes. Yes. The only way one can write secure software is by always using the latest SOTA model. Anything else is inefficient and vulnerable.

      I hate this platform

      2 replies →