• Contend6248@feddit.de
      251·
      1 year ago

      True, when i respond with the exact problem it usually gets fixed, interestingly even explained why it failed.

      Great for learning

      • IzzyScissor@lemmy.world
        23·
        1 year ago

        The only problem is that it’ll ALSO agree if you suggest the wrong problem.

        “Hey, shouldn’t you have to fleem the snort so it can be repurposed for later use?”

        You are correct. Fleeming the snort is necessary for repurposing for later use. Here is the updated code:

        • Rhaedas@kbin.social
          5·
          1 year ago

          Models are geared towards seeking the best human response for answers, not necessarily the answers themselves. Its first answer is based on probability of autocompleting from a huge sample of data, and in versions that have a memory adjusts later responses to how well the human is accepting the answers. There is no actual processing of the answers, although that may be in the latest variations being worked on where there are components that cycle through hundreds of attempts of generations of a problem to try to verify and pick the best answers. Basically rather than spit out the first autocomplete answers, it has subprocessing to actually weed out the junk and narrow into a hopefully good result. Still not AGI, but it’s more useful than the first LLMs.

        • FaceDeer@kbin.social
          3·
          1 year ago

          That’s not been my experience. It’ll tend to be agreeable when I suggest architecture changes, or if I insist on some particular suboptimal design element, but if I tell it “this bit here isn’t working” when it clearly isn’t the real problem I’ve had it disagree with me and tell me what it thinks the bug is really caused by.

      • Opafi@feddit.de
        7·
        1 year ago

        Man, I really was interested in that topic, but that guy really can’t do talks.

        • takeda@lemmy.world
          1·
          1 year ago

          What about this? https://youtu.be/5XY3K8DH55M

          Also I created this repo to create a reproducible sec environment for myself. I added other languages, but personally work mostly with python. It is basically resonating for handling all the boiler plate:

          https://github.com/takeda/nix-cde

          For packaging in docker I started to use nix2container project as it gives me a greater control over layers. So for example when I package my phyton app I typically use 3 layers:

          • python and it’s dependencies
          • my application dependencies
          • my application, which is very tiny compared to other two, so there is great reuse of the layers

          The algorithm mentioned in the video also helps a lot with reuse, but the above is more optimized by frequency of how things typically change.

          BTW: today I discovered this https://github.com/astro/microvm.nix I haven’t play with it yet, but in theory it would let me generate a microvm image (in similar fashion to generate a docker container) which would let me to run my app natively as a tiny VM on EC2 for example, and use only minimum necessary of a typical OS to run it.

  • Fades@lemmy.world
    245·
    1 year ago

    Every time I hear this from one of my devs under me I get a little more angry. Such a meaningless statement, what are you gonna do, hand your pc to the fucking customer?

    • FaceDeer@kbin.social
      28·
      1 year ago

      It’s not actually meaningless. It means “I did test this and it did work under certain conditions.” So maybe if you can determine what conditions are different on the customer’s machine that’ll give you a clue as to what happened.

      The most obscure bug that I ever created ended up being something that would work just fine on any machine that had at any point had Visual Studio 2013 installed on it, even if it had since had it uninstalled (it left behind the library that my code change had introduced a hidden dependency on). It would only fail on a machine that had never had Visual Studio 2013 installed. This was quite a few years back so the computers we had throughout the company mostly had had 2013 installed at some point, only brand new ones that hadn’t been used for much would crash when it happened to touch my code. That was a fun one to figure out and the list of “works on this machine” vs. “doesn’t work on that machine” was useful.