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
    241·
    3 months 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.

    • reabsorbthelight@lemmy.worldOP
      14·
      3 months 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
        7·
        3 months ago

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