If this is the way to superintelligence, it remains a bizarre one. “This is back to a million monkeys typing for a million years generating the works of Shakespeare,” Emily Bender told me. But OpenAI’s technology effectively crunches those years down to seconds. A company blog boasts that an o1 model scored better than most humans on a recent coding test that allowed participants to submit 50 possible solutions to each problem—but only when o1 was allowed 10,000 submissions instead. No human could come up with that many possibilities in a reasonable length of time, which is exactly the point. To OpenAI, unlimited time and resources are an advantage that its hardware-grounded models have over biology. Not even two weeks after the launch of the o1 preview, the start-up presented plans to build data centers that would each require the power generated by approximately five large nuclear reactors, enough for almost 3 million homes.

https://archive.is/xUJMG

  • NocturnalMorning@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    18 days ago

    How is it useful to type millions of solutions out that are wrong to come up with the right one? That only works on a research project when youre searching for patterns. If you are trying to code, it needs to be right the first time every time it’s run, especially if it’s in a production environment.

    • Khanzarate@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      18 days ago

      Well actually there’s ways to automate quality assurance.

      If a programmer reasonably knew that one of these 10,000 files was the “correct” code, they could pull out quality assurance tests and find that code pretty dang easily, all things considered.

      Those tests would eliminate most of the 9,999 wrong ones, and then the QA person could look through the remaining ones by hand. Like a capcha for programming code.

      The power usage still makes this a ridiculous solution.

      • designatedhacker@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        18 days ago

        If you first have to write comprehensive unit/integration tests, then have a model spray code at them until it passes, that isn’t useful. If you spend that much time writing perfect tests, you’ve already written probably twice the code of just the solution and reasonable tests.

        Also you have an unmaintainable codebase that could be a hairball of different code snippets slapped together with dubious copyright.

        Until they hit real AGI this is just fancy auto complete. With the hype they may dissuade a whole generation of software engineers picking a career today. If they don’t actually make it to AGI it will take a long time to recover and humans who actually know how to fix AI slop will make bank.

      • NocturnalMorning@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        18 days ago

        That seems like an awful solution. Writing a QA test for every tiny thing I want to do is going to add far more work to the task. This would increase the workload, not shorten it.

        • Jeena@piefed.jeena.net
          link
          fedilink
          English
          arrow-up
          0
          ·
          18 days ago

          We already have to do that as humans in many industries like automobile, aviation, medicine, etc.

          We have several layers of tests:

          1. Unit test
          2. Component test
          3. Integration / API test
          4. Subsystem test
          5. System test

          On each level we test the code against the requirements and architecture documentation. It’s a huge amount of work.

          In automotive we have several standard processes which need to be followed during development like ASPICE and ISO26262:

          • NocturnalMorning@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            18 days ago

            I’ve worked in both automotive, and the aerospace industry. A unit test is not the same thing as creating a QA script to go through millions of lines of code generated by an AI. Thats such an asinine suggestion. Youve clearly not worked on any practical software application or you’d know this is utter hogwash.

    • Jeena@piefed.jeena.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      18 days ago

      TDD, Test Driven Development. A human writes requirements, with help of the AI he/she derrives tests from the requirements. AI writes code until the tests don’t fail.

      • NocturnalMorning@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        18 days ago

        Yeah, go ahead try that and see how it works out for you. Test driven development is one thing, having an AI try to write the correct code for you by blindly writing code is idiotic.