“No Duh,” say senior developers everywhere.

The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.

  • Sibshops@lemmy.myserv.one
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    21 hours ago

    Fair, I’ve used it recently to translate a translations.ts file to Spanish.

    But for repetitive code, I feel like it is kind of a slow down sometimes. I should have refactored instead.

    • cam_i_am@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      5 hours ago

      This is a thing people miss. “Oh it can generate repetitive code.”

      OK, now who’s going to maintain those thousands of lines of repetitive unit tests, let alone check them for correctness? Certainly not the developer who was too lazy to write their own tests and to think about how to refactor or abstract things to avoid the repetition.

      If someone’s response to a repetitive task is copy-pasting poorly-written code over and over we call them a bad engineer. If they use an AI to do the copy-paste for them that’s supposed to be better somehow?

    • Pennomi@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      2
      ·
      20 hours ago

      Some code is boilerplate and can’t be distilled down more. It’s nice to point an AI to a database schema and say “write the Django models, admin, forms, and api for this schema, using these authentication permissions”. Yeah I’ll have to verify it’s done right, but that gets a lot of the boring typing out of the way.