• SamuraiBeandog@lemmy.world
    link
    fedilink
    English
    arrow-up
    69
    arrow-down
    2
    ·
    3 days ago

    Clickbait title. This is in the context of competitive coding, which is a very specific and constrained programming exercise with a time limit. Which is not at all comparable to real world software development.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      22
      ·
      3 days ago

      I think the problem is, to businesses it is very much comparable. Businesses only ever (and don’t listen to anything they say, that’s all a lie) think about short term revenue gains. If they actually ever planned ahead you’d not have the month end, quarter end and year end revenue panics that seemingly every medium to large organization has.

      So, being able to make decent looking software fast, is actually way more useful to them than it being “good” long term.

      My only hope at this point, is people doing software engineering for as many years as I have can now create “Artisan software” as an art piece or something and get rich from it. :P

      • jubilationtcornpone@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        13
        ·
        3 days ago

        Corporate: Spends millions working frantically to whip together a software project over two years.

        Also Corporate: Kills the project and lays off the entire team two days after release when customers don’t magically flock to the new platform overnight.

        The longer I do this, the more I’m convinced the “M” in MBA actually stands for “Moron”.

    • Kairos@lemmy.today
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      6
      ·
      edit-2
      3 days ago

      Eh. That’s like saying speed chess “is not at all comparable” to chess. There’s differences but it’s the same game. In this case speed coding still relies on the programmers understanding of the problem. There’s just usually less edge cases that you have to handle (usually input can be read in a less safe way because it’s in a specific format, and others)

      • SamuraiBeandog@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        3 days ago

        It’s not the same game at all. A single purpose piece of code does not have the same considerations as a large software application. It’s more like one is speed chess and the other is actual armies on a battlefield.

      • saltesc@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        3 days ago

        It’s more like comparing a review of Chapter 1 to a book report.

        We know a computer is faster at things. It relies on that to perform iterations, overcoming the core shortfall of actual intelligence. Whereas the ideas a human gets are established almost instantly, especially with experience, but they perform slower.

        Literally, this is the “development” in software development.

    • Schal330@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 days ago

      When I originally saw this report on another source, the key standout for me was how many people were beaten by the AI, and the fact the winner was 5% ahead, which really is a small margin. It was being touted as “Yay we beat the AI!” without acknowledging that there were a lot of people that lost to it.