• ILikeBoobies@lemmy.ca
    link
    fedilink
    arrow-up
    106
    ·
    2 months ago

    Vibe coders not understanding their code because they didn’t write it.

    Me not understanding my code because I wrote it a month ago.

    • oatscoop@midwest.social
      link
      fedilink
      arrow-up
      9
      ·
      2 months ago

      My workflow is :

      Step one: write down a bunch of nonsense, massive block comments of old code in case the new code is worse, and cludges in one massive file.

      Step two: rewrite the whole thing: breaking it down into classes so it’s readable and maintainable …

      Step 3: come back later and wonder where the hell anything is. Go to step 1

        • oatscoop@midwest.social
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          I do a lot of fairly complex data processing that benefits from any abstraction I can get.

          E.g. “Take these 50,000 data points, identify and apply the best set of filters for each sections, then produce the best curve fit for each section.” It’s massively complex and (hilariously) produces multiple equally massive data sets while working – acceleration and velocity plots, for example.

    • drexy_rexy@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      Vibe coders not understanding their code because they didn’t write it.

      Me not understanding my code because I wrote it a month ago.

      …we are not the same :P

    • UFO@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      “huh. I wonder how this works? I’ll check with the original dev”

      Checks git blame

      “Well fuck…”