• cockmushroom@reddthat.com
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      3 days ago

      Normally, speed. Especially if you aren’t a picky writer; which you should be; for scenarios like this one.

    • SorryQuick@lemmy.ca
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      3 days ago

      It’s still so much faster. An experienced engineer spoon-feeding the AI the exact logic/algorithm to use is still faster than writing it by hand. I think a lot of people stopped early when AI was worse and/or before they started being good at using it.

        • SorryQuick@lemmy.ca
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          2 days ago

          If you’re getting spaghetti it’s a skill issue.

          If you vibe code, sure you’ll get slop. Ask it to do something to get X result, you’re leaving it room to think so you get slop. Tell it exactly what logic you want it to use, step by step like it’s a child, then you get the same you’d do yourself but faster.

          Look at the PRs for quality-critical projects like the linux kernel and I guarantee you coudn’t tell which PR has some AI and which does not.

        • SorryQuick@lemmy.ca
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          3 days ago

          When you spoon feed it the algorithm, it’s good, at least better than your average programmer. You just have to make sure it doesn’t have too much thinking to do. Honestly people in here really overestimate the talent of most dev.

          There was a comment somewhere I really liked: people thought it would be one junior dev with AI replacing 10 senior ones. In reality, it’s one senior dev with AI replacing 10 junior vibe coders.