• gnutrino@programming.dev
    link
    fedilink
    English
    arrow-up
    11
    ·
    14 hours ago

    On average it’s maybe 15-20% quicker than manually coding the whole lot.

    Out of interest, how much is this 15-20% increase in productivity costing in tokens?

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

      It’d be minimal since I’m doing all the hard work initially and feeding it logic to follow. I find open vibe coding does rip tokens and usually ends up with an overcomplicate mess. Many rabbit holes the AI creates and sends itself down, so a lot more unnecessary lines and often entire redundant blocks.

      If someone’s going to do that, at the least break it up into sections to save tokens and time. But ideally, just get some coding experience under the belt of have a crack at it yourself first so it’s easy to identify the pitfalls and where clear instructions is needed.

    • phutatorius@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      You’d really need to know the fully burdened cost of an hour of the person’s time who’d be doing the work, versus the cost of the tokens plus all the overheads involved in its administration and use of the AI solution (tokens, support, training). Same goes with the downsides-- you’d need to know how the rate of serious bugs changes when you incorporate the slop. Some of the defects will make it through reviews and testing and into prod.