I was handed a pile of vibe code. And you might be surprised to learn that it has a ton of bugs.

And tips on how to dissect it and break it up into something manageable?

  • yaroto98@lemmy.world
    171·
    21 hours ago

    For work, or for hobby?

    Hobby: have AI document what it’s supposed to do, then work through it like the ship of theseus one function at a time replacing it with not bad code.

    Work: use it, document the bugs, ninja in and clear them out one at a time until it works. Keep blinders on and ignore anything not directly related to each bug. Same strategy as legacy code.

    • draco_aeneus@mander.xyz
      3·
      5 hours ago

      The problem with this approach is twofold.

      1. The AI doesn’t know what anything is either. It can annotate faster than you, but if it is all wrong, that doesn’t help.
      2. The primary reason the code is bad, and something the AI is particularly weak at without a human doing much of the thinking for it is architecture. Working your way through ship-of-theseus-style isn’t going to address the fundamental reason the code is difficult to work with. The architecture.
    • reabsorbthelight@lemmy.worldOP
      12·
      21 hours ago

      For work. The code goes like 8 levels of abstraction. I’m trying to figure out how to unravel it.

      Even a code flow/branching diagram would help I think

      • zener_diode@feddit.org
        5·
        20 hours ago

        Depending on the language, there might exist an automated tool for generating those kinds of diagrams from code.