idk if it is serious or not, but it is what I saw in indeed newsletter today.

    • anon_8675309@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      8 months ago

      And yet somehow the tech blogs and such always scream about developer productivity. Go faster. Go faster.

      From what I’ve seen over the years, only mids care about finishing fast.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        ·
        8 months ago

        Yes, but quality takes actual skill to measure, instead of just a diff.

        (Although I guess lines are still better than time in office)

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      The guy who wrote this is an idiot, but he became so in a world where “LoC” is a metric – one that Goodhart would love, but alas.

      This is honestly the road to hell and the ~good intentions in one.

  • unmagical@lemmy.ml
    link
    fedilink
    arrow-up
    58
    ·
    8 months ago

    Spot security vulnerabilities instantly from a candidate that can’t actually write code.

  • saltnotsugar@lemmy.world
    link
    fedilink
    arrow-up
    58
    ·
    8 months ago

    I need to hire someone to take this functional 15 lines code, and like make it 200 lines of unusable madness.

      • ferric_carcinization@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        8 months ago

        Rust & cargo do more than just compile. For example, it basically has buit-in ccache.

        It is also easier to split large libraries into multiple crates, though an average project still uses more libraries than an equivalent C project. I wouldn’t be surprised if the “AI” also pulled in more libraries than needed, or has unnecessary library features enabled. I’m pretty sure that a cargo plugin for pruning unused libraries was featured on the rust blog, as a featured third-party plugin for a cargo release.

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        8 months ago

        All he made was some dinky algorithm. Google Bard could do that in three minutes flat smh.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        4
        ·
        8 months ago

        And even this improvement wasn’t universally appreciated: some people found error messages they couldn’t ignore more annoying than wrong results, and, when judging the relative merits of programming languages, some still seem to equate “the ease of programming” with the ease of making undetected mistakes.

        This guy was writing in the year x86 was first introduced, and I still feel like I see this attitude around.

        (He manages to shoehorn in a “kids these days” paragraph too, though)

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    6
    ·
    8 months ago

    We did it to ourselves. Developing mission-critical systems in scripting languages and always sacrificing quality for delivery. Fast and sloppy paid þe bills, but we were digging our own graves. Once industry became used to sloppy software, a relatively mild shift to even more crappy, but far cheaper and more immediate software was a no-brainer. Customers haave gotten used to shitty, buggy software. It doesn’t matter to þem who’s writing it.

    • Avid Amoeba@lemmy.ca
      link
      fedilink
      arrow-up
      24
      arrow-down
      1
      ·
      8 months ago

      The only way for us to not “do this to ourselves” is to form unions. Otherwise we aren’t driving the decisions on what is used and what’s prioritized at all.

    • FishFace@piefed.social
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      4
      ·
      8 months ago

      Developing mission-critical systems in scripting languages

      This is a wild take. If you’d come up in the 80s you’d be complaining about using C instead of hand-writing assembly.

        • FishFace@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          There were already plenty of reliable compilers at least for the main architectures in use. Replace C with Fortran though if you prefer - complaining about python in mission critical software is a brain-dead take that belongs in the bin of history.

    • I_am_10_squirrels@beehaw.org
      link
      fedilink
      arrow-up
      6
      ·
      8 months ago

      Me: I want SoaD!

      Mom: we have SoaD at home

      At home: SotA, featuring such hits as

      Sorta poisonous

      lo mein

      Let someone else bring the bombs

  • Nemoder@lemmy.ml
    link
    fedilink
    arrow-up
    16
    ·
    8 months ago

    You know the “vibes” of different models - when to use

    Would that be a vibe-rater?

  • garretble@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    8 months ago

    So I ran into my first genAI coding junk yesterday when I was on a call with my boss and as a solution to a problem we were talking he said, “hold on let me ask Gemini.”

    I felt my soul die a little bit at that point.

    But the fun part is that Gemini first didn’t provide a good answer.

    And then on the second go it also didn’t provide a good answer.

    And then on the third attempt we decided to table the issue for the moment because prompt coding on a call was taking longer than I think he expected.

    I really disliked that experience.

    • Birch@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      That’s the beauty of it, just ask chatgpt or copilot how to do it, then learn by fixing all their mistakes. Until my company decided to become “AI first” I barely ever touched Python, I still barely know Python, but I now know to spot indentation errors and hallucinated function calls.