• 1 Post
  • 410 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle



  • The original source was much more sensible.

    The comparison makes sense for evaluating whether you’re over-invested in something. Like, if Nvidia suddenly poofed out of existence, would it seriously be worth 16% of everything the whole country makes in a year to get it back?

    Owning a car that’s worth 16% of your yearly income sounds reasonable, no matter what your actual income is. A Pokemon card collection that’s 16% of your income is probably too risky, no matter what your actual income is.

    Also, GDP is a decent scale to use for charting investment in a productivity tool, because if GDP ramped up at the same time as investment then it looks less like a bubble, even if they both ramp up quickly.

    But that’s not what we see. We see a sudden and volatile shift, nothing like the normal pattern before the hype.




  • It’s the problem, but also the strength. That fragmentation allows room to experiment.

    It also puts pressure on the underlying protocols/specs to be air-tight. If you have just one implementation to support, you can do whatever. If you have to support 15, all with different goals and constraints, you gotta be pretty damn careful.

    So in the end, we get foundational systems that are able to evolve over time instead of needing a breaking-change, ground-up rewrite every 2 years.


  • Think of it like your browser history but for Git. It’s a list of the SHAs related to your recent operations.

    And because Git is a content-addressable data store, a SHA is basically like a URL. Even if a branch no longer exists, if you know the SHA it pointed to then you can still check out the exact contents of that branch. The reflog helps you find that.




  • kibiz0r@midwest.socialtoComic Strips@lemmy.worldAssistants
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    1 month ago

    Ah. Definitely a translation issue. I didn’t realize there was a translation involved. Or that you were the author. I wouldn’t have been so critical otherwise. You’re doing great.

    “Attachment” in general doesn’t have a direction, but in the context of “attach debugger”, it does, because the target of the attachment is the process you want to inspect. In this case, the process is the code you’re writing, not the LLM helping you write it.


  • kibiz0r@midwest.socialtoComic Strips@lemmy.worldAssistants
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    edit-2
    1 month ago

    attached a debugger to the LLM

    interpret the input

    This reads like someone who has heard of these general concepts but doesn’t understand them.

    But then again, I just imagined trying to be 100% accurate while still being concise, and I don’t think it’s possible.

    It’s also not really clear what the dynamic is supposed to be here. Is the LLM supposed to be invoking the generated code through a separate entry point like a test suite, or is the developer launching the built app with a debugger attached and feeding a prompt to the LLM whenever an exception is thrown?

    Neither one of those would really be “attaching a debugger to the LLM” though, and in either case it would be interpreting the output not the input.





  • I’d settle for just requiring interoperability. Seems like a reasonable requirement for a government to demand the ability to change vendors.

    We have that requirement when it comes to munitions. You’re not allowed to sell the military a gun for which you are the only ammo manufacturer.

    A side effect would probably be that more commercial software would be interoperable as a result, just because it’s easier for the vendors to maintain a single product rather than wildly different variants.