“No Duh,” say senior developers everywhere.

The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.

  • RagingRobot@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    9 hours ago

    I have been vibe coding a whole game in JavaScript to try it out. So far I have gotten a pretty ok game out of it. It’s just a simple match three bubble pop type of thing so nothing crazy but I made a design and I am trying to implement it using mostly vibe coding.

    That being said the code is awful. So many bad choices and spaghetti code. It also took longer than if I had written it myself.

    So now I have a game that’s kind of hard to modify haha. I may try to setup some unit tests and have it refactor using those.

      • RagingRobot@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        Blaming? I mean it wrote pretty much all of the code. I definitely wouldn’t tell people I wrote it that way haha.

    • mcv@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 hours ago

      Sounds like vibecoders will have to relearn the lessons of the past 40 years of software engineering.

      • CheeseNoodle@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        4 hours ago

        As with every profession every generation… only this time on their own because every company forgot what employee training is and expects everyone to be born with 5 years of experience.