• 0 Posts
  • 39 Comments
Joined 7 months ago
cake
Cake day: March 3rd, 2026

help-circle

  • I think most of the time with these kind of problems we are comparing apples and oranges. Sure we are both using LLMs to make fruit, but what kind of fruit? I’ve found models are best at what they are most trained for but as soon as you want Kiwi and they aren’t as popular as apples you need to be on your A game. I think people who say LLMs are really good are doing trivial stuff or the most stock standard thing you can think of, like making a new portal web app with the most ubiquitous technologies that have been around forever.







  • Code is probably one of the easiest things to verify, for that reason I struggle to see any other viable uses for LLMs tbh.

    user: write code that correctly asserts what 1+1 equals.
    LLM: assert_eq!(1 + 1, 4);
    LLM: hmmm, that crashed.
    LLM: assert_eq!(1 + 1, 3);
    LLM: hmmm, that also crashed, I must be doing something wrong, let me try one more time.
    LLM: assert_eq!(1 + 1, 2);
    LLM: that worked!
    LLM Response: assert_eq!(1 + 1, 2);
    
    user: what does this sentence mean? "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo"
    LLM Response: This doesn't mean anything, or someone really likes buffalo's
    

    I can always run the code to check, I still don’t know how that sentence makes sense.



  • I think the best analogy to highlight the drawbacks of Rust is to say it’s like “Good test coverage.”. If you read that as 100% test coverage you can spend a lot of time doing some trivial overhead that probably isn’t doing a whole lot. But, if you have half a brain it’s probably not particularly harmful. If you read that as effective test coverage, you probably know the problem quite well and it’s probably some overhead, but you get to feel a bit more confident and have some executable documentation.

    Neither of which I have heard to be useful or converted in the game industry so it sounds like a waste of time.

    That said, if you’re like me and that overhead sounds nice, then you might like Rust :P



  • The edge case is software development, for the bog standard stuff I write at work it probably helps me get work done about 15%-30% faster and with costs of $200-$400 USD a month the math actually works out. At current prices anyway. Also the electricity costs of running open weight models is even cheaper and if there is a pop HW prices may make that an obvious choice too. The worst case IMO would be a slow boil of prices to recoup the unsustainable growth then a slow decline to wherever normal ends up. In that case everyone is left indignant.